From: Michael Meissner <meissner@linux.ibm.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Thomas Koenig <tkoenig@netcologne.de>,
Michael Meissner <meissner@linux.ibm.com>,
Bill Schmidt <wschmidt@linux.ibm.com>,
"fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
Segher Boessenkool <segher@kernel.crashing.org>,
Peter Bergner <bergner@linux.ibm.com>,
David Edelsohn <dje.gcc@gmail.com>,
gcc-patches@gcc.gnu.org
Subject: Re: [power-ieee128] libquadmath: Use -mno-gnu-attribute in libquadmath
Date: Wed, 5 Jan 2022 17:31:20 -0500 [thread overview]
Message-ID: <YdYcOCCLBfRy/F5y@toto.the-meissners.org> (raw)
In-Reply-To: <20220103152450.GK2664@tucnak>
On Mon, Jan 03, 2022 at 04:24:50PM +0100, Jakub Jelinek wrote:
> Hi!
>
> Testing found that we also need libquadmath to be built with
> -mno-gnu-attribute, otherwise -mabi=ieeelongdouble programs don't link.
>
> Ok for power-ieee128?
>
> 2022-01-03 Jakub Jelinek <jakub@redhat.com>
>
> * configure.ac: Set XCFLAGS to -mno-gnu-attribute on
> powerpc64le*-linux*.
> * configure: Regenerated.
I'm wondering whether we want to change things so that Fortran never uses long
double on PowerPC, but instead it explicitly uses __float128 and __ibm128. But
this breaks down in using printf/scanf, which don't have format options for
those types.
Unfortunately this won't work with the current code, since passing any of the
128-bit floating point types causes the flag 'rs6000_passes_long_double' to be
set (and then the gnu attribute #4 is set). In theory, that should be set only
if an explicit long double type is used. But the problem is when those things
are set, you tend to only have modes and not types.
To do it 'right', you probably need a GIMPLE pass that looks at the actual
types used, not the modes.
--
Michael Meissner, IBM
PO Box 98, Ayer, Massachusetts, USA, 01432
email: meissner@linux.ibm.com
prev parent reply other threads:[~2022-01-05 22:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-03 15:24 Jakub Jelinek
2022-01-03 15:58 ` Thomas Koenig
2022-01-05 22:31 ` Michael Meissner [this message]
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=YdYcOCCLBfRy/F5y@toto.the-meissners.org \
--to=meissner@linux.ibm.com \
--cc=bergner@linux.ibm.com \
--cc=dje.gcc@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=segher@kernel.crashing.org \
--cc=tkoenig@netcologne.de \
--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).