This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/15967] [3.4/3.5 regression] ICE on ambiguous operator new in class hierarchy
- From: "giovannibajo at libero dot it" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 15 Jun 2004 00:51:37 -0000
- Subject: [Bug c++/15967] [3.4/3.5 regression] ICE on ambiguous operator new in class hierarchy
- References: <20040612225420.15967.wwieser@gmx.de>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From giovannibajo at libero dot it 2004-06-15 00:51 -------
Subject: Re: [3.4/3.5 regression] ICE on ambiguous operator new in class hierarchy
mark at codesourcery dot com wrote:
> Unless you can prove that returning a TREE_LIST will not result in a
> problem anywhere else -- including other ice-on-invalid cases -- your
> patch is not a win on the release branch.
There is only one other place where lookup_fnfields is called with protect=2,
which is in build_dtor_call(): the value returned is passed directly to
build_new_method_call, which checks for error_operand_p at the very beginning
and returns error_mark_node. lookup_field is *never* called with protect=2.
I think this is a prove.
If you are still not convinced, I will prepare the easy patch for 3.4.
Giovanni Bajo
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15967