public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "reichelt at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/12726] [3.3.2 regression] ICE (segfault) on trivial code
Date: Wed, 22 Oct 2003 19:59:00 -0000	[thread overview]
Message-ID: <20031022195433.14828.qmail@sources.redhat.com> (raw)
In-Reply-To: <20031022170846.12726.mr_W@mindnever.org>

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

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


reichelt at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|normal                      |critical
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|                            |1
           Keywords|                            |ice-on-valid-code
           Priority|P2                          |P1
   Last reconfirmed|0000-00-00 00:00:00         |2003-10-22 19:54:33
               date|                            |
            Summary|ICE (segfault) on trivial   |[3.3.2 regression] ICE
                   |code                        |(segfault) on trivial code
   Target Milestone|---                         |3.3.3


------- Additional Comments From reichelt at gcc dot gnu dot org  2003-10-22 19:54 -------
Indeed. Crashes 3.3.2, but not 3.3.1 or mainline.
Here's a reduced code snippet:

===============================================
struct A
{
    A();
    A(const A&);
    A(int);
};

struct B
{
    A a;
};

void foo()
{
    B b;
    b = (B){0};
}
===============================================

According to Phil's tester, the regression was introduced
between 2003-10-14-3.3 (#246) and 2003-10-15-3.3 (#247).


  parent reply	other threads:[~2003-10-22 19:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-22 17:11 [Bug c++/12726] New: " mr_W at mindnever dot org
2003-10-22 19:16 ` [Bug c++/12726] " bangerth at dealii dot org
2003-10-22 19:59 ` reichelt at gcc dot gnu dot org [this message]
2003-10-22 20:00 ` [Bug c++/12726] [3.3.2/3.4 regression] " reichelt at gcc dot gnu dot org
2003-10-22 20:06 ` reichelt at gcc dot gnu dot org
2003-10-23  6:41 ` cvs-commit at gcc dot gnu dot org
2003-10-23  6:49 ` cvs-commit at gcc dot gnu dot org
2003-10-23  6:51 ` [Bug c++/12726] [3.3.2 " pinskia at gcc dot gnu dot org
2003-10-23  8:18 ` reichelt at gcc dot gnu dot org
2003-10-23 11:35 ` cvs-commit at gcc dot gnu dot org
2003-10-23 14:35 ` [Bug c++/12726] [3.3.2/3.4 " pinskia at gcc dot gnu dot org
2003-10-27 19:08 ` jason at redhat dot com
2003-11-03 21:29 ` cvs-commit at gcc dot gnu dot org
2003-11-26  1:52 ` reichelt at gcc dot gnu dot org
2003-12-03 14:47 ` reichelt at gcc dot gnu dot org
2003-12-08  0:57 ` reichelt 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=20031022195433.14828.qmail@sources.redhat.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).