public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/42999] [4.5 Regression] bogus error: Parameter 'i' at (1) has not been declared or is a variable, which does not reduce to a constant expression Date: Mon, 08 Feb 2010 15:01:00 -0000 [thread overview] Message-ID: <20100208150129.1628.qmail@sourceware.org> (raw) In-Reply-To: <bug-42999-6642@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from burnus at gcc dot gnu dot org 2010-02-08 15:01 ------- I think it regressed between 2010-01-07-r155688 and 2010-01-10-r155780 Jerry, I think that is due to your initializer patch: r155769 | jvdelisle | 2010-01-09 18:47:04 +0100 (Sat, 09 Jan 2010) | 18 lines http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=155769 2010-01-09 Jerry DeLisle <jvdelisle@gcc.gnu.org> PR fortran/20923 PR fortran/32489 [...] * resolve.c (gfc_is_expandable_expr): New function that determiners if array expressions should have their constructors expanded. (gfc_resolve_expr): Use new function to determine whether or not to call gfc_expand_constructor. -- burnus at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jvdelisle at gcc dot gnu dot | |org Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Last reconfirmed|0000-00-00 00:00:00 |2010-02-08 15:01:28 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42999
next prev parent reply other threads:[~2010-02-08 15:01 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-02-08 14:50 [Bug fortran/42999] New: " jv244 at cam dot ac dot uk 2010-02-08 14:51 ` [Bug fortran/42999] " jv244 at cam dot ac dot uk 2010-02-08 15:01 ` burnus at gcc dot gnu dot org [this message] 2010-02-08 15:02 ` dominiq at lps dot ens dot fr 2010-02-08 17:12 ` rguenth at gcc dot gnu dot org 2010-02-09 3:41 ` jvdelisle at gcc dot gnu dot org 2010-02-10 3:31 ` jvdelisle at gcc dot gnu dot org 2010-02-10 3:35 ` jvdelisle at gcc dot gnu dot org 2010-02-10 8:53 ` jv244 at cam dot ac dot uk 2010-02-23 17:07 ` hjl at gcc dot gnu dot 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=20100208150129.1628.qmail@sourceware.org \ --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).