From: Segher Boessenkool <segher@kernel.crashing.org>
To: Michael Meissner <meissner@linux.ibm.com>,
gcc-patches@gcc.gnu.org, David Edelsohn <dje.gcc@gmail.com>,
Bill Schmidt <wschmidt@linux.ibm.com>,
Peter Bergner <bergner@linux.ibm.com>
Subject: Re: [PATCH] PowerPC: Map IEEE 128-bit long double built-in functions
Date: Thu, 10 Dec 2020 15:20:01 -0600 [thread overview]
Message-ID: <20201210212001.GW2672@gate.crashing.org> (raw)
In-Reply-To: <20201119235814.GA322@ibm-toto.the-meissners.org>
Hi!
On Thu, Nov 19, 2020 at 06:58:14PM -0500, Michael Meissner wrote:
> * config/rs6000/rs6000.c (rs6000_mangle_decl_assembler_name): Add
> support for mapping built-in function names for long double
> built-in functions if long double is IEEE 128-bit.
Please write what it does, not "add support". Say what names it maps
to, importantly. You don't need to list all, but what you wrote is
100% contentless.
> diff --git a/gcc/config/rs6000/rs6000.c b/gcc/config/rs6000/rs6000.c
> index a5188553593..35e9c844e17 100644
> --- a/gcc/config/rs6000/rs6000.c
> +++ b/gcc/config/rs6000/rs6000.c
> @@ -27065,57 +27065,128 @@ rs6000_globalize_decl_name (FILE * stream, tree decl)
> library before you can switch the real*16 type at compile time.
>
> We use the TARGET_MANGLE_DECL_ASSEMBLER_NAME hook to change this name. We
> - only do this if the default is that long double is IBM extended double, and
> - the user asked for IEEE 128-bit. */
> + only do this transformation if the __float128 type is enabled. This
> + prevents us from doing the transformation on older 32-bit ports that might
> + have enabled using IEEE 128-bit floating point as the default long double
> + type. */
I still don't understand why you want to support some hypothetical and
untested configuration.
> + /* { dg-final { scan-assembler {\mbl __ynieee128} } } */
This kind of thing does not portably work (the function names can have
various prefixes added).
I cannot understand this code, and it does seem far from obviously
correct. But, okay for trunk if you handle all fallout (and I mean all,
not just "all you consider important").
Segher
next prev parent reply other threads:[~2020-12-10 21:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-19 23:58 Michael Meissner
2020-12-04 4:31 ` Ping " Michael Meissner
2020-12-10 15:27 ` Ping x2: " Michael Meissner
2020-12-10 21:20 ` Segher Boessenkool [this message]
2020-12-11 22:07 ` Michael Meissner
2020-12-11 23:03 ` Segher Boessenkool
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=20201210212001.GW2672@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=bergner@linux.ibm.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=meissner@linux.ibm.com \
--cc=wschmidt@linux.ibm.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).