This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/61536] [4.10 regression] g++ and libstdc++ regressions on arm-none-linux-gnueabihf with missing typeinfo
- From: "ramana at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Tue, 17 Jun 2014 21:43:12 +0000
- Subject: [Bug libstdc++/61536] [4.10 regression] g++ and libstdc++ regressions on arm-none-linux-gnueabihf with missing typeinfo
- Auto-submitted: auto-generated
- References: <bug-61536-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61536
--- Comment #12 from Ramana Radhakrishnan <ramana at gcc dot gnu.org> ---
(In reply to Paolo Carlini from comment #9)
> Well, up to you really: maybe operator!= is special for you because it just
> thinly wraps operator== which is exported for you. If adding back *only*
> that additional export under the macro works, all your tests are fine, it
> would be great. Otherwise, just revert. Sorry again for the breakage.
Hmm, looks like the patchlet might be enough to do the trick. It looks like I
misread the logs. Apologies, the link time failure was actually with == in
In function `std::type_info::operator!=(std::type_info const&) const':
/work/gcc/libstdc++-v3/testsuite/18_support/type_info/hash_code.cc:51:
undefined reference to `std::type_info::operator==(std::type_info const&)
const'
Looks like it fixes my issue on ARM.
regards
Ramana