public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/47023] C_Sizeof: Rejects valid code Date: Tue, 18 Oct 2011 13:46:00 -0000 [thread overview] Message-ID: <bug-47023-4-aHm72OZCWO@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-47023-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47023 --- Comment #23 from janus at gcc dot gnu.org 2011-10-18 13:45:32 UTC --- (In reply to comment #22) > (In reply to comment #21) > > The question is also how SIZEOF should act on data pointers: > > Should it give the size of the pointer itself, or the size of the object it > > points to? > > The target/pointee. Reasoning: For your example, g95, gfortran, ifort and > pathf95 all print "2". That's also what gfortran claims to do at > http://gcc.gnu.org/onlinedocs/gfortran/SIZEOF.html Well, ok. "Wer lesen kann ist klar im Vorteil" ;) Then this is obviously a feature and not a bug. > Regarding (comment 19, comment 20): > print *,sizeof(proc) ! (1) -- prints 1 > print *,sizeof(pp) ! (2) -- prints 1 > print *,sizeof(pp(0.)) ! (3) -- prints 4 > > ifort rejects (1) and (2) and returns "4" for (3). I think gfortran should do > likewise. Returning the pointee size for scalar variables but the pointer size > of functions is also a bit odd. Ok, I agree that it's better to reject it under these circumstances. How about the following patch? Index: gcc/fortran/check.c =================================================================== --- gcc/fortran/check.c (revision 180134) +++ gcc/fortran/check.c (working copy) @@ -3446,8 +3446,15 @@ gfc_check_size (gfc_expr *array, gfc_expr *dim, gf gfc_try -gfc_check_sizeof (gfc_expr *arg ATTRIBUTE_UNUSED) +gfc_check_sizeof (gfc_expr *arg) { + if (arg->ts.type == BT_PROCEDURE) + { + gfc_error ("'%s' argument of '%s' intrinsic at %L may not be a procedure", + gfc_current_intrinsic_arg[0]->name, gfc_current_intrinsic, + &arg->where); + return FAILURE; + } return SUCCESS; }
next prev parent reply other threads:[~2011-10-18 13:46 UTC|newest] Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-12-20 8:59 [Bug fortran/47023] New: " burnus at gcc dot gnu.org 2010-12-22 10:28 ` [Bug fortran/47023] " burnus at gcc dot gnu.org 2011-09-20 11:47 ` florian.rathgeber at gmail dot com 2011-09-20 15:36 ` [Bug fortran/47023] [4.6/4.7 regression] " kargl at gcc dot gnu.org 2011-09-20 15:40 ` kargl at gcc dot gnu.org 2011-09-20 16:49 ` dominiq at lps dot ens.fr 2011-09-29 13:12 ` burnus at gcc dot gnu.org 2011-09-29 13:20 ` rguenth at gcc dot gnu.org 2011-09-29 13:21 ` burnus at gcc dot gnu.org 2011-09-29 13:29 ` janus at gcc dot gnu.org 2011-09-29 15:52 ` burnus at gcc dot gnu.org 2011-10-16 8:44 ` janus at gcc dot gnu.org 2011-10-16 19:43 ` janus at gcc dot gnu.org 2011-10-17 9:47 ` janus at gcc dot gnu.org 2011-10-17 16:00 ` janus at gcc dot gnu.org 2011-10-17 16:16 ` [Bug fortran/47023] " janus at gcc dot gnu.org 2011-10-17 19:11 ` janus at gcc dot gnu.org 2011-10-17 19:23 ` janus at gcc dot gnu.org 2011-10-18 10:48 ` janus at gcc dot gnu.org 2011-10-18 11:07 ` janus at gcc dot gnu.org 2011-10-18 12:04 ` janus at gcc dot gnu.org 2011-10-18 12:18 ` janus at gcc dot gnu.org 2011-10-18 12:20 ` janus at gcc dot gnu.org 2011-10-18 12:48 ` burnus at gcc dot gnu.org 2011-10-18 13:46 ` janus at gcc dot gnu.org [this message] 2011-10-19 22:08 ` janus at gcc dot gnu.org 2011-10-19 22:10 ` janus at gcc dot gnu.org 2013-03-25 15:53 ` burnus at gcc dot gnu.org 2013-03-25 17:46 ` burnus at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-47023-4-aHm72OZCWO@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).