public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Paul E Murphy <murphyp@linux.ibm.com>
To: Florian Weimer <fw@deneb.enyo.de>,
	"Paul E. Murphy via Libc-alpha" <libc-alpha@sourceware.org>
Subject: Re: [PATCH v3 1/6] ldbl-128ibm-compat: workaround GCC 9 C++ BZ 90731
Date: Wed, 22 Apr 2020 16:17:19 -0500	[thread overview]
Message-ID: <4f8dcbea-1485-3d3c-b896-8da95a90de4e@linux.ibm.com> (raw)
In-Reply-To: <87zhb3imh4.fsf@mid.deneb.enyo.de>



On 4/22/20 10:11 AM, Florian Weimer wrote:
> * Paul E. Murphy via Libc-alpha:
> 
>> GCC 9 has a bug (BZ 90731) whereby __typeof does not correctly copy
>> exception specifiers[1].  Surprisingly, this can be quieted by declaring
>> "#pragma system_header", or if the headers are installed in a system
>> directory.
> 
> I think GCC developers prefer “PR90731” to their bugs.  This occurs
> multiple times in the commit message and throughout the patch.

Ack.  Will fix here and in the subsequent patches too.

> 
> This change will still cause errors with -Wsystem-headers in the build
> flags, right?  I think we should mention this somewhere, maybe on the
> release wiki?
> 

Unfortunately, ppc64le glibc will fail to build with GCC 9.2.0 with this 
option irrespective of this feature.  Though, you are correct the 
redirects will generate additional warnings when used with such toolchains.

Likewise, --disable-werror does avoid breaking things when using 
-Wsystem-headers.  The warnings are not fatal.

I suspect the -Wsystem-headers will cause some noise for most users with 
GCC 8/9 and likely others.  I can add a note, but I suspect I will need 
to be granted wiki editing privileges.

  reply	other threads:[~2020-04-22 21:17 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-06 19:12 [PATCH v3 0/6] IEEE binary128 long double on powerpc64le Paul E. Murphy
2020-04-06 19:12 ` [PATCH v3 1/6] ldbl-128ibm-compat: workaround GCC 9 C++ BZ 90731 Paul E. Murphy
2020-04-15 14:20   ` Paul E Murphy
2020-04-22 14:58     ` Paul E Murphy
2020-04-22 15:11   ` Florian Weimer
2020-04-22 21:17     ` Paul E Murphy [this message]
2020-04-23  5:48       ` Florian Weimer
2020-04-06 19:12 ` [PATCH v3 2/6] Rename __LONG_DOUBLE_USES_FLOAT128 to __LDOUBLE_REDIRECTS_TO_FLOAT128_ABI Paul E. Murphy
2020-04-15 14:21   ` Paul E Murphy
2020-04-22 14:59     ` Paul E Murphy
2020-04-06 19:12 ` [PATCH v3 3/6] powerpc64le: raise GCC requirement to 7.4 for long double transition Paul E. Murphy
2020-04-22 15:19   ` Florian Weimer
2020-04-22 19:33     ` Paul E Murphy
2020-04-06 19:12 ` [PATCH v3 4/6] powerpc64le: bump binutils version requirement to >= 2.26 Paul E. Murphy
2020-04-22 15:20   ` Florian Weimer
2020-04-06 19:12 ` [PATCH v3 5/6] powerpc64le: blacklist broken GCC compilers (e.g GCC 7.5.0) Paul E. Murphy
2020-04-22 15:23   ` Florian Weimer
2020-04-06 19:12 ` [PATCH v3 6/6] powerpc64le: Enable support for IEEE long double Paul E. Murphy
2020-04-22 15:03   ` Paul E Murphy
2020-04-22 15:15   ` Florian Weimer
2020-04-22 16:20     ` Paul E Murphy
2020-04-22 16:23       ` 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=4f8dcbea-1485-3d3c-b896-8da95a90de4e@linux.ibm.com \
    --to=murphyp@linux.ibm.com \
    --cc=fw@deneb.enyo.de \
    --cc=libc-alpha@sourceware.org \
    /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).