public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Paul E Murphy <murphyp@linux.ibm.com>
Cc: DJ Delorie via Libc-alpha <libc-alpha@sourceware.org>,
	 DJ Delorie <dj@redhat.com>,
	 Tulio Magno Quites Machado Filho <tuliom@linux.vnet.ibm.com>,
	 "Paul E. Murphy" <murphyp@linux.vnet.ibm.com>
Subject: Re: ppc64le: gcc 12 vs -mabi=ibmlongdouble
Date: Mon, 24 Jan 2022 18:56:22 +0100	[thread overview]
Message-ID: <8735ld2f21.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <ea28d47b-cfbb-7027-043f-f354cf450437@linux.ibm.com> (Paul E. Murphy's message of "Mon, 24 Jan 2022 11:46:54 -0600")

* Paul E. Murphy:

> On 1/24/22 9:38 AM, Florian Weimer 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?
>
> For the sake of my clarification, does this affect more than the 6
> test cases/files in ldbl-opt Makefile? If not, could the removal be
> handled case-by-case in sysdeps/powerpc/powerpc64/le/Makefile?

That's what I tried in my patch, but it seems to interact negatively
with other make constructs, so any CFLAGS-*.c settings stop working for
these targets.

Thanks,
Florian


      reply	other threads:[~2022-01-24 17:56 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
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 [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=8735ld2f21.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=dj@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=murphyp@linux.ibm.com \
    --cc=murphyp@linux.vnet.ibm.com \
    --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).