From: Tobias Burnus <tobias@codesourcery.com>
To: Sandra Loosemore <sandra@codesourcery.com>,
"fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH, Fortran] Use _Float128 rather than __float128 for c_float128 kind
Date: Fri, 17 Sep 2021 10:27:47 +0200 [thread overview]
Message-ID: <db86e4c1-241b-28a0-6204-b6f6f31f56ae@codesourcery.com> (raw)
In-Reply-To: <98e74d66-7214-64c3-579c-6fafbb78aa37@codesourcery.com>
On 17.09.21 06:02, Sandra Loosemore wrote:
> On 9/5/21 11:20 PM, Sandra Loosemore wrote:
>> Unless the aarch64 maintainers think it is a bug that __float128 is
>> not supported, I think the right solution here is [...] to tie the
>> C_FLOAT128 kind to _Float128 rather than __float128, [...]
>
> Here's a new patch that does this. I've tested it on
> x86_64-linux-gnu, powerpc64le-linux-gnu, and aarch64-linux-gnu, and it
> does fix the previously reported failure compiling
> gfortran.dg/PR100914.c on aarch64. OK to commit?
LGTM – thanks!
Tobias
-----------------
Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht München, HRB 106955
prev parent reply other threads:[~2021-09-17 8:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-05 2:30 [PATCH, Fortran] Skip gfortran.dg/PR100914.f90 on targets that don't provide quadmath.h Sandra Loosemore
2021-09-05 13:31 ` H.J. Lu
2021-09-05 18:02 ` Sandra Loosemore
2021-09-06 1:29 ` H.J. Lu
2021-09-06 5:20 ` Sandra Loosemore
2021-09-06 7:06 ` Christophe Lyon
2021-09-06 10:18 ` Tobias Burnus
2021-09-06 16:31 ` Joseph Myers
2021-09-17 4:02 ` [PATCH, Fortran] Use _Float128 rather than __float128 for c_float128 kind Sandra Loosemore
2021-09-17 8:27 ` Tobias Burnus [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=db86e4c1-241b-28a0-6204-b6f6f31f56ae@codesourcery.com \
--to=tobias@codesourcery.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=sandra@codesourcery.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).