public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jvdelisle at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/41807] [4.5/4.4 Regression] data statement with nested type constructors Date: Tue, 17 Nov 2009 04:18:00 -0000 [thread overview] Message-ID: <20091117041752.25968.qmail@sourceware.org> (raw) In-Reply-To: <bug-41807-10374@http.gcc.gnu.org/bugzilla/> ------- Comment #14 from jvdelisle at gcc dot gnu dot org 2009-11-17 04:17 ------- The offending patch is in 4.4 r148732, r148731 passes the test case. --- branches/gcc-4_4-branch/gcc/fortran/resolve.c 2009/04/03 20:56:54 145519 +++ branches/gcc-4_4-branch/gcc/fortran/resolve.c 2009/06/19 22:10:45 148732 @@ -9430,9 +9430,12 @@ static gfc_try next_data_value (void) { - while (mpz_cmp_ui (values.left, 0) == 0) { + if (!gfc_is_constant_expr (values.vnode->expr)) + gfc_error ("non-constant DATA value at %L", + &values.vnode->expr->where); + if (values.vnode->next == NULL) return FAILURE; I suspect that gfc_is_constant_expr is clobbering something. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41807
next prev parent reply other threads:[~2009-11-17 4:18 UTC|newest] Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-10-23 12:27 [Bug fortran/41807] New: [Reg] " pault at gcc dot gnu dot org 2009-10-23 12:46 ` [Bug fortran/41807] " dominiq at lps dot ens dot fr 2009-10-24 7:46 ` [Bug fortran/41807] [4.5, 4.4 Regression] " pault at gcc dot gnu dot org 2009-10-24 9:38 ` pault at gcc dot gnu dot org 2009-10-24 11:51 ` [Bug fortran/41807] [4.5/4.4 " rguenth at gcc dot gnu dot org 2009-11-06 14:07 ` burnus at gcc dot gnu dot org 2009-11-06 15:02 ` dominiq at lps dot ens dot fr 2009-11-06 16:12 ` jvdelisle at gcc dot gnu dot org 2009-11-11 5:21 ` jvdelisle at gcc dot gnu dot org 2009-11-14 18:35 ` jvdelisle at gcc dot gnu dot org 2009-11-14 19:30 ` kargl at gcc dot gnu dot org 2009-11-14 19:32 ` kargl at gcc dot gnu dot org 2009-11-14 21:24 ` jvdelisle at gcc dot gnu dot org 2009-11-15 18:38 ` kargl at gcc dot gnu dot org 2009-11-15 19:05 ` jvdelisle at gcc dot gnu dot org 2009-11-15 19:26 ` sgk at troutmask dot apl dot washington dot edu 2009-11-17 4:18 ` jvdelisle at gcc dot gnu dot org [this message] 2009-11-17 4:30 ` jvdelisle at gcc dot gnu dot org 2009-11-17 5:35 ` jvdelisle at gcc dot gnu dot org 2009-11-17 6:03 ` sgk at troutmask dot apl dot washington dot edu 2009-11-21 22:15 ` jvdelisle at gcc dot gnu dot org 2009-11-22 2:05 ` jvdelisle at gcc dot gnu dot org 2009-11-22 2:06 ` jvdelisle at gcc dot gnu dot org 2009-11-22 2:10 ` jvdelisle at gcc dot gnu dot org 2009-11-25 2:38 ` jvdelisle at gcc dot gnu dot org 2009-11-25 2:45 ` jvdelisle at gcc dot gnu dot org 2009-11-25 3:34 ` jvdelisle at gcc dot gnu dot org 2009-11-26 1:08 ` jvdelisle at gcc dot gnu dot org 2009-11-26 2:12 ` jvdelisle at gcc dot gnu dot org 2009-11-26 21:53 ` jvdelisle at gcc dot gnu dot org 2009-11-26 21:57 ` jvdelisle at gcc dot gnu dot org 2009-11-26 22:19 ` jvdelisle at gcc dot gnu dot org 2009-11-26 22:21 ` jvdelisle at gcc dot gnu dot org 2009-11-27 8:32 ` burnus 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=20091117041752.25968.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).