public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pault at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/36703] ICE (segfault) in reduce_binary0 (arith.c:1778) Date: Thu, 12 Feb 2009 09:19:00 -0000 [thread overview] Message-ID: <20090212091921.23131.qmail@sourceware.org> (raw) In-Reply-To: <bug-36703-13404@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from pault at gcc dot gnu dot org 2009-02-12 09:19 ------- (In reply to comment #1) Interestingly, if the WRITE statement is cut, the compilation now fails with: pr36703.f90: In function 'gp': pr36703.f90:46: internal compiler error: in expand_expr_real_1, at expr.c:7282 This corresponds to the line: __result_gp = get_funloc (make_mess, aux, ..__result); and the declaration of get_funloc is: get_funloc (void (*<T193>) (character(kind=1)[0:][1:.x] * &, integer(kind=4), st ruct array01_integer(kind=4) &) x, void (*<T5b>) (void) (*<T181>) (void) y, inte ger(kind=4) _x) { void (*<T5b>) (void) __result_get_funloc; __result_get_funloc = y (x); return __result_get_funloc; } which looks OK. The ICE is generated by - context = decl_function_context (exp); gcc_assert (!context || context = current_function_decl || TREE_STATIC (exp) /* ??? C++ creates functions that are not TREE_STATIC. */ || TREE_CODE (exp) == FUNC_DECL); I have not checked yet but I would guess that it is the latter that is the problem. Paul -- pault at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pault at gcc dot gnu dot org Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Last reconfirmed|0000-00-00 00:00:00 |2009-02-12 09:19:21 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36703
next prev parent reply other threads:[~2009-02-12 9:19 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-07-02 20:25 [Bug fortran/36703] New: " burnus at gcc dot gnu dot org 2008-07-02 20:27 ` [Bug fortran/36703] " burnus at gcc dot gnu dot org 2009-02-12 9:19 ` pault at gcc dot gnu dot org [this message] 2009-02-13 12:53 ` pault at gcc dot gnu dot org 2009-02-13 21:13 ` pault at gcc dot gnu dot org 2009-03-28 17:09 ` pault at gcc dot gnu dot org 2009-04-06 11:08 ` pault 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=20090212091921.23131.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).