https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83834
--- Comment #14 from Jonathan Wakely ---
Author: redi
Date: Tue Jan 16 12:43:08 2018
New Revision: 256739
URL: https://gcc.gnu.org/viewcvs?rev=256739=gcc=rev
Log:
PR libstdc++/83834 replace wildcard pattern in linker script
PR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83834
Jonathan Wakely changed:
What|Removed |Added
Status|NEW |ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83834
--- Comment #12 from nsz at gcc dot gnu.org ---
(In reply to Jonathan Wakely from comment #10)
> This should fix it:
>
> --- a/libstdc++-v3/config/abi/pre/gnu.ver
> +++ b/libstdc++-v3/config/abi/pre/gnu.ver
> @@ -58,9 +58,7 @@ GLIBCXX_3.4 {
> #
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83834
--- Comment #11 from Jonathan Wakely ---
(In reply to Jonathan Wakely from comment #10)
> It looks like the std::c[a-z] pattern only matches one symbol anyway:
Typo, I meant std::c[a-g]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83834
--- Comment #10 from Jonathan Wakely ---
It looks like the std::c[a-z] pattern only matches one symbol anyway:
"std::cerr"
This should fix it:
--- a/libstdc++-v3/config/abi/pre/gnu.ver
+++ b/libstdc++-v3/config/abi/pre/gnu.ver
@@ -58,9 +58,7
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83834
--- Comment #9 from Jonathan Wakely ---
There's no "correct" answer, the exact form of the demangled string is somewhat
arbitrary, especially for lambdas as there is no way to say that name in C++.
The libstdc++ linker script clearly expected
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83834
--- Comment #8 from nsz at gcc dot gnu.org ---
ok it's because of 'void f()' vs 'f()'
old:
8133 cxx_sym = bfd_demangle (link_info.output_bfd, sym,
Value returned is $2 = 0x2695a00 "void std::call_once >(std::once_flag&, void
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83834
nsz at gcc dot gnu.org changed:
What|Removed |Added
CC||nsz at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83834
--- Comment #6 from H.J. Lu ---
This may be due to binutils 2.30:
https://sourceware.org/ml/binutils/2018-01/msg00236.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83834
--- Comment #5 from H.J. Lu ---
I updated glibc on Fedora 27 on Friday.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83834
--- Comment #4 from H.J. Lu ---
(In reply to Jakub Jelinek from comment #3)
> So, what exact symbols does it report as incompatible?
> I can't reproduce with my build from Friday late evening on both targets.
It happened during weekend:
2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83834
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83834
Richard Biener changed:
What|Removed |Added
Target||x86_64-*-*, i?86-*-*
Target
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83834
H.J. Lu changed:
What|Removed |Added
CC||jwakely.gcc at gmail dot com
--- Comment #2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83834
H.J. Lu changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
15 matches
Mail list logo
