public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/45044] Different named COMMON block size: No warning Date: Tue, 30 Aug 2011 21:48:00 -0000 [thread overview] Message-ID: <bug-45044-4-MYzKeaiINu@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-45044-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45044 --- Comment #4 from Tobias Burnus <burnus at gcc dot gnu.org> 2011-08-30 21:33:18 UTC --- I was thinking of using: gfc_gsymbol *gsym; gsym = gfc_get_gsymbol (com->name); gcc_assert (gsym->type == GSYM_COMMON); gfc_warning ("Named COMMON block '%s' at %L shall be of the " "same size as at %L (%lu vs %lu bytes)", com->name, &com->where, &gsym->where, But that won't work reliably: a) The byte size changes, while the position of (2) remains the same, e.g: Warnung: Named COMMON block 'xx' at (1) shall be of the same size as at (2) (24 vs 4 bytes) Warnung: Named COMMON block 'xx' at (1) shall be of the same size as at (2) (8 vs 24 bytes) b) One get's even strange results if one has 4 bytes, 30 bytes, 4 bytes as then (1) and (2) have the same bytes size but the error message claims that one is 4 and the other is 30 bytes wide. I defer this and now only print the byte-size, cf. http://gcc.gnu.org/ml/fortran/2011-08/msg00254.html
next prev parent reply other threads:[~2011-08-30 21:33 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-45044-4@http.gcc.gnu.org/bugzilla/> 2011-03-09 13:38 ` dominiq at lps dot ens.fr 2011-08-30 13:27 ` burnus at gcc dot gnu.org 2011-08-30 13:28 ` burnus at gcc dot gnu.org 2011-08-30 21:48 ` burnus at gcc dot gnu.org [this message] 2011-08-30 23:00 ` burnus at gcc dot gnu.org 2011-10-09 19:38 ` burnus at gcc dot gnu.org 2011-10-10 6:54 ` burnus at gcc dot gnu.org 2014-01-13 15:13 ` dominiq at lps dot ens.fr 2014-01-13 15:44 ` dominiq at lps dot ens.fr
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-45044-4-MYzKeaiINu@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).