From: Bill Schmidt <wschmidt@linux.ibm.com>
To: Florian Weimer <fweimer@redhat.com>,
DJ Delorie via Libc-alpha <libc-alpha@sourceware.org>
Cc: Tulio Magno Quites Machado Filho <tuliom@linux.vnet.ibm.com>
Subject: Re: ppc64le: gcc 12 vs -mabi=ibmlongdouble
Date: Mon, 24 Jan 2022 10:44:23 -0600 [thread overview]
Message-ID: <de1b9209-3bf8-54dd-9295-da19a55bf4da@linux.ibm.com> (raw)
In-Reply-To: <87bl012lfs.fsf@oldenburg.str.redhat.com>
I ran this by our GCC team, and the tentative consensus is that
-mlong-double-64 should override -mabi=ibmlongdouble, rather than
reporting an error in the compile flags. DJ, could you please
open a bug against the GCC powerpc target?
Thanks!
Bill
On 1/24/22 9:38 AM, Florian Weimer via Libc-alpha wrote:
> * DJ Delorie via Libc-alpha:
>
>> I've been working on updating glibc for Fedora Rawhide, and have
>> stumbled upon this issue (after working around the -Wuse-after-free
>> issues with a cflags hack)... A few of the math tests explicitly add
>> -mlong-double-64 but configure adds -mabi=ibmlongdouble
>>
>> I would guess that we need a "CFLAGS -= -mabi=ibmlongdouble" in all
>> the places we add -mlong-double-64 but I don't see an easy way of
>> doing that, nor am I sure that's a valid solution. Alternately, gcc
>> could be changed to accept the conflicting flags in a meaningful way,
>> if there is one. Is there an -mabi= that undoes the
>> -mabi=ibmlongdouble that we can just add to the -mlong-double-64 flag
>> lines?
>> cc1: error: '-mabi=ibmlongdouble' requires '-mlong-double-128'
> I was able to reproduce with a GCC 12 build configured using
> --with-long-double-format=ieee.
>
> I tried the attached patch to remove the unwanted -mabi=ibmlongdouble,
> but it does not work: it removes CFLAGS-*.c processing as a side effect.
>
> Any suggestions how we can fix this properly?
>
> Thanks,
> Florian
next prev parent reply other threads:[~2022-01-24 16:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-22 6:34 DJ Delorie
2022-01-24 15:38 ` Florian Weimer
2022-01-24 16:44 ` Bill Schmidt [this message]
2022-01-24 18:32 ` Florian Weimer
2022-01-24 17:37 ` Adhemerval Zanella
2022-01-24 17:46 ` Paul E Murphy
2022-01-24 17:56 ` Florian Weimer
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=de1b9209-3bf8-54dd-9295-da19a55bf4da@linux.ibm.com \
--to=wschmidt@linux.ibm.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=tuliom@linux.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).