Invalid code generated from release 1.1.1 and snapshot 19990228

Martin v. Loewis martin@mira.isdn.cs.tu-berlin.de
Wed Mar 31 23:54:00 GMT 1999


> thanks for the clarification. If the rules for mangling
> array types did intentionally change, please just take 
> it as a bug report for c++filt then.

I'm not sure whether it was intentional. AFAICT, it was changed in

1998-07-21  Jason Merrill  <jason@yorick.cygnus.com>

	* tree.c (canonical_type_variant): New fn to handle arrays.
	* cp-tree.h (CANONICAL_TYPE_VARIANT): Remove.
	* pt.c (unify, default case): Also fold arg.  Fix array bounds case.
	* method.c (process_overload_item): Use build_overload_value for
	arrays.

Under -fsquangling, it will change back. Whether it was intentional or
not: Compatibility to more recent versions is probably more important
than compatibility to 2.7.2 (which we don't have, anyway).

Unfortunately, there is no way for c++filt to know what the convention
is, so I guess that also stays as-is.

Regards,
Martin



More information about the Gcc-bugs mailing list