From: Wilco Dijkstra <Wilco.Dijkstra@arm.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: "libc-alpha@sourceware.org" <libc-alpha@sourceware.org>, nd <nd@arm.com>
Subject: Re: [PATCH] Use fabs(f/l) rather than __fabs
Date: Fri, 29 Sep 2017 18:34:00 -0000 [thread overview]
Message-ID: <DB6PR0801MB2053ADFC56A678C3C97DAFBB837E0@DB6PR0801MB2053.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1709291623180.25795@digraph.polyomino.org.uk>
Joseph Myers wrote:
> I think you need to add -fno-builtin-fabsl for e_lgammal_r.c, e_log10l.c
> and e_log2l.c in sysdeps/powerpc/nofpu/Makefile, for the same reason as
> the existing -fno-builtin-fabsl uses there - the built-in fabsl does not
> work properly for signed zero for powerpc soft-float / e500v1 (and the
> uses of __fabsl being changed are all uses that need to work correctly for
> signed zero).
Done, I verified that glibcs-powerpc-linux-gnu-soft now builds those files with
-fno-builtin-fabsl and that it passes.
> To be clear, the reason the change is safe regarding namespace issues is
> that the particular functions in question don't get called from C90
> functions in the case where fabsl might not be inlined (which is only the
> powerpc soft-float / e500v1 case where -fno-builtin-fabsl is needed); the
> existence of fabsl calls from other functions is not sufficient. There is
> code to call ldbl-128ibm expl from pow, but that's not one of the affected
> functions and that code doesn't apply for soft-float / e500v1 anyway.
> (fabsl is in fact a reserved name in C90, but the linknamespace tests
> don't know that.)
Right so there are no namespace issues. But what about localplt issues
due to the disabling of fabsl inlining? I can't find any renaming, so why are
there no local plt failures on ppc soft-float?
Wilco
next prev parent reply other threads:[~2017-09-29 18:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-29 13:02 Wilco Dijkstra
2017-09-29 16:30 ` Joseph Myers
2017-09-29 18:34 ` Wilco Dijkstra [this message]
2017-09-29 19:56 ` Joseph Myers
2017-09-29 20:00 ` Gabriel F. T. Gomes
2017-10-03 14:33 ` Szabolcs Nagy
2017-10-03 15:49 ` Szabolcs Nagy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DB6PR0801MB2053ADFC56A678C3C97DAFBB837E0@DB6PR0801MB2053.eurprd08.prod.outlook.com \
--to=wilco.dijkstra@arm.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=nd@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).