public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bangerth@dealii.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org,
	rassahah@cs.tu-berlin.de
Subject: Re: optimization/8913: [3.3 regression] ICE in simplify_gen_subreg, at simplify-rtx.c
Date: Thu, 12 Dec 2002 07:09:00 -0000	[thread overview]
Message-ID: <20021212150913.19462.qmail@sources.redhat.com> (raw)

Old Synopsis: internal compiler error: in simplify_gen_subreg, at simplify-rtx.c
New Synopsis: [3.3 regression] ICE in simplify_gen_subreg, at simplify-rtx.c

State-Changed-From-To: open->analyzed
State-Changed-By: bangerth
State-Changed-When: Thu Dec 12 07:09:12 2002
State-Changed-Why:
    Confirmed. This is a regression, 3.2 compiled it fine.
    A slightly smaller testcase is
    -------------------
    template <class T> struct Ref { 
        Ref(int *);
        ~Ref();
    };
    
    struct User{
        User (Ref<int> obj) {};
    };
     
    void test() {
      User a (0);
    }
    -----------------------
    yielding
    tmp/g> /home/bangerth/bin/gcc-3.3-pre/bin/c++ -O -c x.cc
    x.cc: In function `void test()':
    x.cc:7: internal compiler error: in simplify_gen_subreg, at simplify-rtx.c:2673
    Please submit a full bug report,
    with preprocessed source if appropriate.
    See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
    
    My compiler collection tells me that the regression was
    introduced after Dec 1st this year, i.e. very recently.
    

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8913


             reply	other threads:[~2002-12-12 15:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-12  7:09 bangerth [this message]
2002-12-12 17:06 Janis Johnson
2003-01-11 16:46 Craig Rodrigues
2003-03-24 20:04 steven

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=20021212150913.19462.qmail@sources.redhat.com \
    --to=bangerth@dealii.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    --cc=rassahah@cs.tu-berlin.de \
    /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).