public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Tulio Magno Quites Machado Filho <tuliom@linux.ibm.com>
To: Michael Meissner via Gcc <gcc@gcc.gnu.org>,
	GCC Development <gcc@gcc.gnu.org>,
	Michael Meissner <meissner@linux.ibm.com>,
	Segher Boessenkool <segher@kernel.crashing.org>,
	"Kewen.Lin" <linkw@linux.ibm.com>,
	David Edelsohn <dje.gcc@gmail.com>,
	Peter Bergner <bergner@linux.ibm.com>,
	Will Schmidt <will_schmidt@vnet.ibm.com>,
	Jason Merrill <jason@redhat.com>, Nathan Sidwell <nathan@acm.org>,
	Mike Stump <mikestump@comcast.net>,
	Iain Sandoe <iain@sandoe.co.uk>,
	Joseph Myers <joseph@codesourcery.com>,
	Alan Modra <amodra@gmail.com>, Nick Clifton <nickc@redhat.com>,
	Jeff Law <jlaw@tachyum.com>, Jakub Jelinek <jakub@redhat.com>,
	Richard Biener <rguenther@suse.de>,
	"David S. Miller" <davem@redhat.com>,
	"Carlos O'Donell" <carlos@redhat.com>,
	libc-alpha@sourceware.org
Subject: Re: Resend: Potential upcoming changes in mangling to PowerPC GCC
Date: Wed, 10 Aug 2022 16:55:42 -0300	[thread overview]
Message-ID: <871qtnc1q9.fsf@linux.ibm.com> (raw)
In-Reply-To: <YuwGg08djkg6iFQc@toto.the-meissners.org>

Michael Meissner via Gcc <gcc@gcc.gnu.org> writes:

> Because long double mangles the same as either __float128 or __ibm128, you
> cannot write programs like:
>
> 	double convert (__ibm128    x) { return x; }
> 	double convert (__float128  x) { return x; }
> 	double convert (long double x) { return x; }
>
> You would have to write on a system with long double being IBM 128-bit:
>
> 	double convert (__float128  x) { return x; }
> 	double convert (long double x) { return x; }
>
> or on a system with long double being IEEE 128-bit:
>
> 	double convert (__ibm128    x) { return x; }
> 	double convert (long double x) { return x; }

Does that mean, when long double is IEEE 128-bit, the compiler won't support
_Float128/__float128 ?

-- 
Tulio Magno

  parent reply	other threads:[~2022-08-10 19:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-04 17:48 Michael Meissner
2022-08-04 20:53 ` Segher Boessenkool
2022-08-08 21:44   ` Michael Meissner
2022-08-10 17:14     ` Segher Boessenkool
2022-08-10 19:55 ` Tulio Magno Quites Machado Filho [this message]
2022-08-10 20:04   ` Segher Boessenkool
2022-08-10 21:38     ` Tulio Magno Quites Machado Filho

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=871qtnc1q9.fsf@linux.ibm.com \
    --to=tuliom@linux.ibm.com \
    --cc=amodra@gmail.com \
    --cc=bergner@linux.ibm.com \
    --cc=carlos@redhat.com \
    --cc=davem@redhat.com \
    --cc=dje.gcc@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=iain@sandoe.co.uk \
    --cc=jakub@redhat.com \
    --cc=jason@redhat.com \
    --cc=jlaw@tachyum.com \
    --cc=joseph@codesourcery.com \
    --cc=libc-alpha@sourceware.org \
    --cc=linkw@linux.ibm.com \
    --cc=meissner@linux.ibm.com \
    --cc=mikestump@comcast.net \
    --cc=nathan@acm.org \
    --cc=nickc@redhat.com \
    --cc=rguenther@suse.de \
    --cc=segher@kernel.crashing.org \
    --cc=will_schmidt@vnet.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).