--- Comment #32 from carlos at codesourcery dot com 2009-04-29 15:07
---
No, you are absolutely right and the tree dumps confirm it. I thought it might
be possible to trigger a reference by using the right flags, but to no avail,
the compiler always folds the if-then-else to __signbit.
--- Comment #28 from carlos at codesourcery dot com 2009-04-28 20:57
---
Exporting a non-default versioned symbol is useless since new programs won't be
able to link against that definition.
Did 4.2/4.3 export a global default symbol for __signbitl?
If we did export a global default
--- Comment #29 from jakub at gcc dot gnu dot org 2009-04-28 23:56 ---
The glibc macro AFAIK does:
# define signbit(x) \
(sizeof (x) == sizeof (float)\
? __signbitf (x)\
--- Comment #30 from jakub at gcc dot gnu dot org 2009-04-28 23:59 ---
Also, libstdc++.so is definitely not the right home for __signbitl symbol, so
we definitely shouldn't allow any newly linked program to use symbol from that
library. If __signbitl is ever needed (prove it), then it
--- Comment #31 from dave at hiauly1 dot hia dot nrc dot ca 2009-04-29
01:03 ---
Subject: Re: [4.2/4.3 regression] symbol __signb...@glibcxx_3.4 in libstdc++
exported
Also, libstdc++.so is definitely not the right home for __signbitl symbol, so
we definitely shouldn't allow any
--- Comment #27 from bkoz at gcc dot gnu dot org 2009-04-27 22:46 ---
2) Someone please add a stub to libstdc++ for __signb...@glibcxx_3.4 that
calls
__signbitl in glibc.
Hmm. Well, you cannot actually add a new symbol versioned for the first release
in the ninth release. That is
6 matches
Mail list logo
