public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c++/31138]  New: [4.3 regression] ICE with ellipsis
@ 2007-03-11 22:09 reichelt at gcc dot gnu dot org
  2007-03-11 22:09 ` [Bug c++/31138] " reichelt at gcc dot gnu dot org
                   ` (8 more replies)
  0 siblings, 9 replies; 10+ messages in thread
From: reichelt at gcc dot gnu dot org @ 2007-03-11 22:09 UTC (permalink / raw)
  To: gcc-bugs

The following valid code snippet triggers an ICE on mainline:

=====================
void foo(long ...);
=====================

bug.cc:1: internal compiler error: Segmentation fault
Please submit a full bug report, [etc.]

The same thing happens for the following invalid variation:

=====================
void foo(const ...);
=====================


-- 
           Summary: [4.3 regression] ICE with ellipsis
           Product: gcc
           Version: 4.3.0
            Status: UNCONFIRMED
          Keywords: ice-on-valid-code, ice-on-invalid-code, monitored
          Severity: normal
          Priority: P3
         Component: c++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: reichelt at gcc dot gnu dot org


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


^ permalink raw reply	[flat|nested] 10+ messages in thread

end of thread, other threads:[~2007-03-31 12:44 UTC | newest]

Thread overview: 10+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-03-11 22:09 [Bug c++/31138] New: [4.3 regression] ICE with ellipsis reichelt at gcc dot gnu dot org
2007-03-11 22:09 ` [Bug c++/31138] " reichelt at gcc dot gnu dot org
2007-03-11 23:01 ` reichelt at gcc dot gnu dot org
2007-03-11 23:19 ` pinskia at gcc dot gnu dot org
2007-03-11 23:51 ` schwab at suse dot de
2007-03-27 14:12 ` doug dot gregor at gmail dot com
2007-03-27 14:18 ` tbm at gcc dot gnu dot org
2007-03-28 14:31 ` dgregor at gcc dot gnu dot org
2007-03-31 12:42 ` dgregor at gcc dot gnu dot org
2007-03-31 12:44 ` dgregor at gcc dot gnu dot org

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).