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 23:00:00 -0000 [thread overview] Message-ID: <bug-45044-4-tTIhUvOkCu@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 #5 from Tobias Burnus <burnus at gcc dot gnu.org> 2011-08-30 22:09:55 UTC --- Author: burnus Date: Tue Aug 30 22:09:49 2011 New Revision: 178344 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=178344 Log: 2011-08-30 Tobias Burnus <burnus@net-b.de> PR fortran/45044 * trans-common.c (build_common_decl): Warn if named common block's size is not everywhere the same. 2011-08-30 Tobias Burnus <burnus@net-b.de> PR fortran/45044 * gfortran.dg/common_14.f90: New. * gfortran.dg/common_resize_1.f: Add two dg-warning. Added: trunk/gcc/testsuite/gfortran.dg/common_14.f90 Modified: trunk/gcc/fortran/ChangeLog trunk/gcc/fortran/trans-common.c trunk/gcc/testsuite/ChangeLog trunk/gcc/testsuite/gfortran.dg/common_resize_1.f
next prev parent reply other threads:[~2011-08-30 22:10 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 2011-08-30 23:00 ` burnus at gcc dot gnu.org [this message] 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-tTIhUvOkCu@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).