[Bug c++/11105] [3.3/3.4 regression of sorts] ICE in mangle_conv_op_name_for_type

mmitchel at gcc dot gnu dot org gcc-bugzilla@gcc.gnu.org
Thu Aug 7 17:34:00 GMT 2003


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

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


mmitchel at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|                            |FIXED


------- Additional Comments From mmitchel at gcc dot gnu dot org  2003-08-07 17:34 -------
This patch removed the erroneous manglings.

It is true that there are some functions whose manglings might change, but only
where those manglings could have collided with other functions before.

There is no way to win here.

The regression we had before was that perfectly legal code that worked fine with
GCC 2.95 couldn't be correctly compiled; now it compiles, but it is perhaps
mangled differently than GCC 3.2.

This is the same kind of ABI change that you get when you find out that you're
passing two arguments to a function in the same stack slot.  If you don't fix
it, your compiler is horribly broken.



More information about the Gcc-bugs mailing list