From: Jonathan Wakely <jwakely@redhat.com>
To: Bernd Edlinger <bernd.edlinger@hotmail.de>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
"libstdc++@gcc.gnu.org" <libstdc++@gcc.gnu.org>
Subject: Re: [PATCH] Make cstddef / cstdarg more robust (PR 69881)
Date: Tue, 23 Feb 2016 09:42:00 -0000 [thread overview]
Message-ID: <20160223094232.GE3171@redhat.com> (raw)
In-Reply-To: <HE1PR07MB0905BE8B57CCF6328BE2A52FE4A40@HE1PR07MB0905.eurprd07.prod.outlook.com>
On 23/02/16 07:15 +0000, Bernd Edlinger wrote:
>as described in the PR 69881 it happens quite often that cstddef is
>called with __need_size_t because we still support gmp-4.3.2 which
>is installed by contrib/download_prerequisites. This causes a kind
>of undefined behavior. It is just by chance that this does not cause
>the gcc-6 boot-strap to fail, but it causes gcc-4.9 bootstrap to fail
>when the gcc-6 version of cstddef is around. So it looks like a
>regression, because the new cstddef is more fragile than before.
Is it? cstddef hasn't been changed since 2013-06-11. cstdarg hasn't
been changed since 2011-01-30.
What made them more fragile?
next prev parent reply other threads:[~2016-02-23 9:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-23 7:15 Bernd Edlinger
2016-02-23 9:42 ` Jonathan Wakely [this message]
2016-02-23 10:01 ` Bernd Edlinger
2016-02-23 10:09 ` Jakub Jelinek
2016-02-23 10:20 ` Jonathan Wakely
2016-02-23 10:16 ` Jonathan Wakely
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=20160223094232.GE3171@redhat.com \
--to=jwakely@redhat.com \
--cc=bernd.edlinger@hotmail.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@gcc.gnu.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).