public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/54940] [4.6/4.7/4.8 Regression] ICE in gfc_build_intrinsic_call, at fortran/expr.c:4609
Date: Wed, 17 Oct 2012 19:22:00 -0000 [thread overview]
Message-ID: <bug-54940-4-frvGR1rUNq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54940-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54940
janus at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |janus at gcc dot gnu.org
--- Comment #2 from janus at gcc dot gnu.org 2012-10-17 19:22:34 UTC ---
(In reply to comment #1)
> The ICE starts with 4.6.3. The ICE occurs at
>
> gcc_assert (result->symtree
> && (result->symtree->n.sym->attr.flavor == FL_PROCEDURE
> || result->symtree->n.sym->attr.flavor == FL_UNKNOWN));
>
> introduced by r183314
... which was Tobias' fix for PR 51904. I think the most straightforward thing
would be to just remove the assert again:
Index: gcc/fortran/expr.c
===================================================================
--- gcc/fortran/expr.c (revision 192392)
+++ gcc/fortran/expr.c (working copy)
@@ -4606,9 +4606,6 @@ gfc_build_intrinsic_call (const char* name, locus
result->value.function.isym = isym;
result->symtree = gfc_find_symtree (gfc_current_ns->sym_root, name);
- gcc_assert (result->symtree
- && (result->symtree->n.sym->attr.flavor == FL_PROCEDURE
- || result->symtree->n.sym->attr.flavor == FL_UNKNOWN));
va_start (ap, numarg);
atail = NULL;
In a valid-code context the assert surely makes sense, but here it seems to
choke on the fallout of the two errors.
next prev parent reply other threads:[~2012-10-17 19:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-16 21:40 [Bug fortran/54940] New: " slayoo at staszic dot waw.pl
2012-10-16 22:08 ` [Bug fortran/54940] [4.6/4.7/4.8 Regression] " dominiq at lps dot ens.fr
2012-10-17 19:22 ` janus at gcc dot gnu.org [this message]
2012-11-25 15:58 ` rguenth at gcc dot gnu.org
2012-11-29 8:42 ` jakub at gcc dot gnu.org
2013-01-07 15:24 ` 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-54940-4-frvGR1rUNq@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: link
Be 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).