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 middle-end/41713]  New: -O -flto -g: ICE in lto_output_tree_ref, at lto-streamer-out.c:732
Date: Thu, 15 Oct 2009 08:28:00 -0000	[thread overview]
Message-ID: <bug-41713-13404@http.gcc.gnu.org/bugzilla/> (raw)

$ gfortran -O -flto -g -c test.f
test.f: In function 'makenumberstring_':
test.f:8:0: internal compiler error: in lto_output_tree_ref, at
lto-streamer-out.c:732

That's with Rev. 152840 (and thus later then Rev. 152767 which fixed PR 41521).

Reduced testcase:

      FUNCTION makenumberstring(x)
      IMPLICIT NONE
      REAL, INTENT(IN)     :: x
      CHARACTER(len=20)      :: makenumberstring
      INTEGER             :: xx
      xx = x**2  ! << ICE
      makenumberstring = ''
      END FUNCTION


-- 
           Summary: -O -flto -g: ICE in lto_output_tree_ref, at lto-
                    streamer-out.c:732
           Product: gcc
           Version: 4.5.0
            Status: UNCONFIRMED
          Keywords: ice-on-valid-code, lto
          Severity: normal
          Priority: P3
         Component: middle-end
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: burnus at gcc dot gnu dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41713


             reply	other threads:[~2009-10-15  8:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-15  8:28 burnus at gcc dot gnu dot org [this message]
2009-10-16  9:04 ` [Bug middle-end/41713] " rguenth at gcc dot gnu dot org
2009-10-16 11:41 ` rguenth at gcc dot gnu dot org
2009-10-16 14:21 ` rguenth at gcc dot gnu dot org
2009-10-16 14:24 ` rguenth 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=bug-41713-13404@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).