public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bangerth at dealii dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/15967] [3.4/3.5 regression] ICE on ambiguous operator new in class hierarchy
Date: Sat, 12 Jun 2004 23:22:00 -0000 [thread overview]
Message-ID: <20040612232250.6461.qmail@sourceware.org> (raw)
In-Reply-To: <20040612225420.15967.wwieser@gmx.de>
------- Additional Comments From bangerth at dealii dot org 2004-06-12 23:22 -------
Confirmed. The code is invalid, but the ICE is a regression. Up to
3.3.x we got this:
g/x> /home/bangerth/bin/gcc-3.3.4-pre/bin/c++ -c x.cc
x.cc: In function `int crash()':
x.cc:10: error: request for member `operator new' is ambiguous
x.cc:4: error: candidates are: static void* B::operator new(unsigned int)
x.cc:3: error: static void* A::operator new(unsigned int)
W.
--
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Ever Confirmed| |1
Keywords| |ice-on-invalid-code
Known to fail| |3.4.0 3.5.0
Known to work| |3.3.4
Last reconfirmed|0000-00-00 00:00:00 |2004-06-12 23:22:48
date| |
Summary|ICE: Segmentation fault |[3.4/3.5 regression] ICE on
| |ambiguous operator new in
| |class hierarchy
Target Milestone|--- |3.4.2
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15967
next prev parent reply other threads:[~2004-06-12 23:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-12 22:54 [Bug c++/15967] New: ICE: Segmentation fault wwieser at gmx dot de
2004-06-12 23:22 ` bangerth at dealii dot org [this message]
2004-06-14 2:37 ` [Bug c++/15967] [3.4/3.5 regression] ICE on ambiguous operator new in class hierarchy giovannibajo at libero dot it
2004-06-14 10:46 ` giovannibajo at libero dot it
2004-06-14 14:15 ` mark at codesourcery dot com
2004-06-14 20:16 ` jason at gcc dot gnu dot org
2004-06-14 23:51 ` giovannibajo at libero dot it
2004-06-15 0:04 ` mark at codesourcery dot com
2004-06-15 0:51 ` giovannibajo at libero dot it
2004-06-15 0:59 ` mark at codesourcery dot com
2004-06-15 1:13 ` giovannibajo at libero dot it
2004-06-15 1:46 ` cvs-commit at gcc dot gnu dot org
2004-06-15 3:14 ` cvs-commit at gcc dot gnu dot org
2004-06-15 3:15 ` giovannibajo at libero dot it
2004-06-19 16:16 ` danglin at gcc dot gnu dot org
2004-06-19 16:25 ` pinskia at gcc dot gnu dot org
2004-07-01 20:58 ` andreas dot meier_ at gmx dot de
2004-07-01 20:58 ` 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=20040612232250.6461.qmail@sourceware.org \
--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).