public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gerald at pfeifer dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/16131] New: internal compiler error: in create_tmp_var, at gimplify.c:361
Date: Tue, 22 Jun 2004 08:38:00 -0000	[thread overview]
Message-ID: <20040622083851.16131.gerald@pfeifer.com> (raw)

Recent changes (< 48 hours) on mainline cause GCC to ICE when compiling the
well-known test case from PR8361:

% gccvs  8361.ii generate.C: In member function `bool  
MODEL_GENERATOR::onlyOneUndefAtomGreaterThanUpperGuard(constAGGREGATEATOM&,
constGINTERPRET&) const':
generate.C:3233: internal compiler error: in create_tmp_var, at gimplify.c:361

(This testcase is http://gcc.gnu.org/bugzilla/attachment.cgi?id=4415&action=view)

-- 
           Summary: internal compiler error: in create_tmp_var, at
                    gimplify.c:361
           Product: gcc
           Version: 3.5.0
            Status: UNCONFIRMED
          Severity: critical
          Priority: P2
         Component: tree-optimization
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: gerald at pfeifer dot com
                CC: gcc-bugs at gcc dot gnu dot org
 GCC build triplet: i686-pc-linux-gnu
  GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu
OtherBugsDependingO 8361
             nThis:


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


             reply	other threads:[~2004-06-22  8:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-22  8:38 gerald at pfeifer dot com [this message]
2004-06-22  8:49 ` [Bug tree-optimization/16131] " gerald at pfeifer dot com
2004-06-22 15:10 ` [Bug tree-optimization/16131] [3.5 Regression] " pinskia at gcc dot gnu dot org
2004-06-22 18:25 ` kenner at vlsi1 dot ultra dot nyu dot edu
2004-06-25  4:06 ` pinskia 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=20040622083851.16131.gerald@pfeifer.com \
    --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).