This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH], PowerPC long double transistion, patch #1
On Tue, 19 Jun 2018, Segher Boessenkool wrote:
> > Because the names depend on the format not the type, there is no risk of
> > ABI inconsistency from linking with a libgcc function for the wrong
> > format, and so I think the linker warning is never relevant for linking
> > with libgcc (and once the glibc support is in, it won't be relevant for
> > linking with glibc either). Linker warnings are relevant for the generic
> > case of a library that *doesn't* do anything special to support both
> > formats simultaneously - not for a library that properly handles getting
> > things right for both formats automatically.
>
> Yes. And as far as I see the same is true for *all* libgcc functions
> (not only long double), so we can just as well turn off the gnu_attributes
> warning for all of libgcc.
Yes. libgcc and (future) glibc don't need that warning.
(As I noted in <https://gcc.gnu.org/ml/gcc-patches/2018-06/msg01092.html>
there *is* currently a bug where some *tf* and *tc* functions get built
with the wrong ABI if you change the default long double format.)
--
Joseph S. Myers
joseph@codesourcery.com
- References:
- [PATCH], PowerPC long double transistion, patch #1
- Re: [PATCH], PowerPC long double transistion, patch #1
- Re: [PATCH], PowerPC long double transistion, patch #1
- Re: [PATCH], PowerPC long double transistion, patch #1
- Re: [PATCH], PowerPC long double transistion, patch #1