https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88684
--- Comment #7 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #6)
> I'd check what would they say about upstream change and if they are strongly
> against, make a local change. Even when clang++ is used with libstdc++ the
> default is still strcmp, dunno about libc++.
I'll prepare patch for it.
Btw. according to git grep:
$ git grep __GXX_MERGED_TYPEINFO_NAMES
gcc/config/arm/symbian.h: builtin_define
("__GXX_MERGED_TYPEINFO_NAMES=0"); \
gcc/config/i386/cygming.h: builtin_define
("__GXX_MERGED_TYPEINFO_NAMES=0"); \
gcc/config/m68k/uclinux.h: builtin_define
("__GXX_MERGED_TYPEINFO_NAMES=0"); \
libstdc++-v3/doc/html/manual/api.html:in <code
class="filename">typeinfo</code>, <code
class="literal">__GXX_MERGED_TYPEINFO_NAMES</code>
libstdc++-v3/doc/xml/manual/evolution.xml:in <filename
class="headerfile">typeinfo</filename>,
<literal>__GXX_MERGED_TYPEINFO_NAMES</literal>
libstdc++-v3/libsupc++/tinfo.cc:#if __GXX_MERGED_TYPEINFO_NAMES
libstdc++-v3/libsupc++/tinfo2.cc:#if __GXX_MERGED_TYPEINFO_NAMES
libstdc++-v3/libsupc++/typeinfo:// __GXX_MERGED_TYPEINFO_NAMES to 1 or 0 to
indicate whether or not pointer
libstdc++-v3/libsupc++/typeinfo:#ifndef __GXX_MERGED_TYPEINFO_NAMES
libstdc++-v3/libsupc++/typeinfo:#define __GXX_MERGED_TYPEINFO_NAMES 0
libstdc++-v3/libsupc++/typeinfo: #if !__GXX_MERGED_TYPEINFO_NAMES
libstdc++-v3/libsupc++/typeinfo:# if !__GXX_MERGED_TYPEINFO_NAMES
There are 3 header files that define __GXX_MERGED_TYPEINFO_NAMES=0 (which is
default): can that be removed?
And as __GXX_MERGED_TYPEINFO_NAMES is default, should I create a patch that
will always use strcmp in libsanitizer?
