From: Michael Meissner <meissner@linux.ibm.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: 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>,
Will Schmidt <will_schmidt@vnet.ibm.com>
Subject: Re: [PATCH], PR target/99708 - Define __SIZEOF_FLOAT128__ and __SIZEOF_IBM128__
Date: Tue, 15 Feb 2022 15:18:30 -0500 [thread overview]
Message-ID: <YgwKltVMK7Uien7L@toto.the-meissners.org> (raw)
In-Reply-To: <20220215194506.GC614@gate.crashing.org>
On Tue, Feb 15, 2022 at 01:45:06PM -0600, Segher Boessenkool wrote:
> On Tue, Feb 15, 2022 at 12:49:41PM -0500, Michael Meissner wrote:
> > Define __SIZEOF_FLOAT128__ and __SIZEOF_IBM128__.
> >
> > Define the sizes of the PowerPC specific types __float128 and __ibm128 if those
> > types are enabled.
>
> This is very silly of course, both of these are 16 bytes. Abusing this
> to see if the types exist is at least as silly (there are much better
> mechanisms to do this).
This is just trying to close out the PR that people asked for.
> So, this facilitates bad habits and bad code. But, whatever, the macros
> are just stating totally obvious and redundant facts, no problem, let's
> just ignore that pepople only want it to abuse it.
>
> > gcc/
> > PR target/99708
> > * config/rs6000/rs6000-c.cc (rs6000_target_modify_macros): Define
> > __SIZEOF_FLOAT128__ and __SIZEOF_IBM128__ if we have float128
> > support.
>
> No. __SIZEOF_IBM128__ should be defined if and only if __ibm128 is
> defined.
In the current implementation, __ibm128 is only defined if __float128 was
defined. I did have patches 6 months or so to define __ibm128 on any system
with IBM 128-bit long double. But those were never applied to the trunk.
> This should be tested directly, it should not depend on that some other
> code did what it does today. That would also make the code much more
> obvious.
Given __float128 and __ibm128 are defined at the same time, I don't see the
need for a separate target-supports.exp test, and so forth. But if you want
that, I can easily do it.
--
Michael Meissner, IBM
PO Box 98, Ayer, Massachusetts, USA, 01432
email: meissner@linux.ibm.com
next prev parent reply other threads:[~2022-02-15 20:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 17:49 Michael Meissner
2022-02-15 19:45 ` Segher Boessenkool
2022-02-15 20:18 ` Michael Meissner [this message]
2022-02-15 22:05 ` Segher Boessenkool
2022-02-15 23:05 ` Michael Meissner
2022-02-16 10:28 ` 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=YgwKltVMK7Uien7L@toto.the-meissners.org \
--to=meissner@linux.ibm.com \
--cc=bergner@linux.ibm.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=segher@kernel.crashing.org \
--cc=will_schmidt@vnet.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).