From: Jakub Jelinek <jakub@redhat.com>
To: Thomas Koenig <tkoenig@netcologne.de>
Cc: 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>,
Michael Meissner <meissner@linux.ibm.com>
Subject: Re: [RFC] User-visible changes for powerpc64-le-linux ABI changes
Date: Mon, 1 Nov 2021 18:45:33 +0100 [thread overview]
Message-ID: <20211101174533.GV304296@tucnak> (raw)
In-Reply-To: <7cee9ce9-7fea-4d2d-5c53-e5d708f93c6b@netcologne.de>
On Mon, Nov 01, 2021 at 06:32:51PM +0100, Thomas Koenig wrote:
> f->value.function.name
> = gfc_get_string (PREFIX ("matmul_%c%d"), gfc_type_letter (f->ts.type),
> f->ts.kind);
>
> Easy enough to add something there if ts.type is BT_REAL,
> ts.kind is 16 and the compiler is currently using
> double double (for example), or just use KIND=15 then
> (although that would only be a naming convention).
Note, if we go the way of C/C++ with -mabi=ieeelongdouble vs.
-mabi=ibmlongdouble choosing between the two ABIs and libgfortran being
ABI compatible with both, then we don't need to bump soname.
But, if we don't bump it, we need to keep double double there backwards
compatible (i.e. _r16 etc. being the double double, not IEEE).
When in the future we bump the soname, we can swap those two and
make _r16 newly stand for IEEE quad and _r15 or _r16d or whatever
for double double.
Jakub
next prev parent reply other threads:[~2021-11-01 17:45 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-31 14:43 Thomas Koenig
2021-11-01 15:54 ` Bill Schmidt
2021-11-01 17:32 ` Thomas Koenig
2021-11-01 17:45 ` Jakub Jelinek [this message]
2021-11-02 6:19 ` Thomas Koenig
2021-11-04 4:41 ` Michael Meissner
2021-11-01 18:46 ` Michael Meissner
2021-11-15 20:27 ` Thomas Koenig
2021-11-15 22:14 ` Peter Bergner
2021-11-15 23:42 ` Michael Meissner
2021-11-16 7:51 ` Thomas Koenig
2021-11-19 14:19 ` Jakub Jelinek
2021-11-19 17:30 ` Segher Boessenkool
2021-11-19 19:09 ` Thomas Koenig
2021-11-19 19:36 ` Peter Bergner
2021-11-19 21:30 ` Segher Boessenkool
2022-01-02 22:58 ` [power-iee128] How to specify linker flags Thomas Koenig
2022-01-03 10:19 ` Thomas Koenig
2022-01-03 10:33 ` Jakub Jelinek
2022-01-03 15:23 ` [power-iee128] libgfortran: Use -mno-gnu-attribute in libgfortran Jakub Jelinek
2022-01-03 15:27 ` Thomas Koenig
2022-01-03 10:34 ` [power-iee128] How to specify linker flags Segher Boessenkool
2022-01-05 21:20 ` Michael Meissner
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=20211101174533.GV304296@tucnak \
--to=jakub@redhat.com \
--cc=bergner@linux.ibm.com \
--cc=dje.gcc@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=meissner@linux.ibm.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).