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/51800] [4.6/4.7 Regression] Error: Automatic array 'dummy' at (1) cannot have an initializer Date: Mon, 09 Jan 2012 18:35:00 -0000 [thread overview] Message-ID: <bug-51800-4-4WwTJzlLPL@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-51800-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51800 Tobias Burnus <burnus at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |rejects-valid CC| |burnus at gcc dot gnu.org, | |toon at moene dot org Known to work| |4.6.2 Target Milestone|--- |4.6.3 Summary|Error: Automatic array |[4.6/4.7 Regression] Error: |'dummy' at (1) cannot have |Automatic array 'dummy' at |an initializer |(1) cannot have an | |initializer Known to fail| |4.7.0 --- Comment #1 from Tobias Burnus <burnus at gcc dot gnu.org> 2012-01-09 18:34:52 UTC --- I think that's due to the patch for PR 51310, i.e. the patches: [4.7] http://gcc.gnu.org/ml/fortran/2011-12/msg00080.html [4.6] http://gcc.gnu.org/ml/fortran/2011-12/msg00119.html Toon, can you have a look?
next prev parent reply other threads:[~2012-01-09 18:35 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-01-09 18:23 [Bug fortran/51800] New: " mario-baumann at web dot de 2012-01-09 18:35 ` burnus at gcc dot gnu.org [this message] 2012-01-09 23:40 ` [Bug fortran/51800] [4.6/4.7 Regression] " jakub at gcc dot gnu.org 2012-01-11 15:04 ` burnus at gcc dot gnu.org 2012-01-11 16:07 ` burnus at gcc dot gnu.org 2012-01-14 12:28 ` burnus at gcc dot gnu.org 2012-01-14 14:20 ` burnus at gcc dot gnu.org 2012-01-14 15:44 ` 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-51800-4-4WwTJzlLPL@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).