https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62018
--- Comment #25 from Francois-Xavier Coudert fxcoudert at gcc dot gnu.org ---
(In reply to Iain Sandoe from comment #23)
2. we have so many versions, different layouts and version-specific issues,
that I think it's time to reorganise our GCC
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62018
--- Comment #26 from Francois-Xavier Coudert fxcoudert at gcc dot gnu.org ---
Created attachment 34077
-- https://gcc.gnu.org/bugzilla/attachment.cgi?id=34077action=edit
Patch removing 10.4 and earlier support from our specs/driver
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62018
--- Comment #27 from Iain Sandoe iains at gcc dot gnu.org ---
(In reply to Francois-Xavier Coudert from comment #25)
(In reply to Iain Sandoe from comment #23)
2. we have so many versions, different layouts and version-specific issues,
that
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62018
--- Comment #28 from howarth at bromo dot med.uc.edu ---
(In reply to Iain Sandoe from comment #27)
10.7+ - (albeit 10.7 is somewhat transitionary)
here we need to stop building the eh stuff into libgcc, we probably need to
split the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62018
--- Comment #12 from rguenther at suse dot de rguenther at suse dot de ---
On Sun, 9 Nov 2014, fxcoudert at gcc dot gnu.org wrote:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62018
--- Comment #8 from Francois-Xavier Coudert fxcoudert at
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62018
--- Comment #13 from rguenther at suse dot de rguenther at suse dot de ---
On Sun, 9 Nov 2014, fxcoudert at gcc dot gnu.org wrote:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62018
Francois-Xavier Coudert fxcoudert at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62018
--- Comment #14 from Francois-Xavier Coudert fxcoudert at gcc dot gnu.org ---
(In reply to rguent...@suse.de from comment #12)
So I bet apple GCC 4.2 is affected as well - not sure if LLVM
provides libgcc_s on newer systems.
Apple does not
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62018
--- Comment #15 from rguenther at suse dot de rguenther at suse dot de ---
On Mon, 10 Nov 2014, fxcoudert at gcc dot gnu.org wrote:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62018
--- Comment #14 from Francois-Xavier Coudert fxcoudert at
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62018
--- Comment #16 from Francois-Xavier Coudert fxcoudert at gcc dot gnu.org ---
(In reply to rguent...@suse.de from comment #15)
Your example directly calling __addvsi3 should suffice for that.
I've filed it (radar #18924081), but I don't expect
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62018
--- Comment #17 from Iain Sandoe iains at gcc dot gnu.org ---
(In reply to Francois-Xavier Coudert from comment #16)
(In reply to rguent...@suse.de from comment #15)
Your example directly calling __addvsi3 should suffice for that.
I've
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62018
--- Comment #18 from Francois-Xavier Coudert fxcoudert at gcc dot gnu.org ---
(In reply to Iain Sandoe from comment #17)
if it's part of compiler-rt we can just post a patch on llvm-commits and
that will eventually percolate through to the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62018
--- Comment #19 from Francois-Xavier Coudert fxcoudert at gcc dot gnu.org ---
(In reply to Iain Sandoe from comment #17)
if it's part of compiler-rt we can just post a patch on llvm-commits and
that will eventually percolate through to the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62018
howarth at bromo dot med.uc.edu changed:
What|Removed |Added
CC||howarth at bromo dot
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62018
--- Comment #21 from Francois-Xavier Coudert fxcoudert at gcc dot gnu.org ---
True, we could also follow this approach again
(https://gcc.gnu.org/bugzilla/show_bug.cgi?id=42333#c55), but it's more of a
hack really.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62018
--- Comment #22 from howarth at bromo dot med.uc.edu ---
(In reply to Francois-Xavier Coudert from comment #21)
True, we could also follow this approach again
(https://gcc.gnu.org/bugzilla/show_bug.cgi?id=42333#c55), but it's more of a
hack
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62018
--- Comment #23 from Iain Sandoe iains at gcc dot gnu.org ---
My take is:
1. It's good we have an upstream patch - if it percolates through that's one
less thing to worry about - although (of course) that will never realistically
be available
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62018
--- Comment #24 from howarth at bromo dot med.uc.edu ---
I always thought the major reorganization would be forced whenever Apple
finally fully deprecated the libgcc_s.10.5.dylib stub, the associated
libgcc_s.10.4.dylib symlink pointing at
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62018
Francois-Xavier Coudert fxcoudert at gcc dot gnu.org changed:
What|Removed |Added
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62018
--- Comment #10 from Iain Sandoe iains at gcc dot gnu.org ---
(In reply to Francois-Xavier Coudert from comment #9)
Some more debugging, and finally a victory: I understand what happens. But I
don't know how to fix it.
0. With my testcase
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62018
--- Comment #11 from Francois-Xavier Coudert fxcoudert at gcc dot gnu.org ---
(In reply to Iain Sandoe from comment #10)
ld64 should pull the symbol from the first place that mentions it on the
link line. It should place the two-level
20 matches
Mail list logo
