bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Bruno Haible <bruno@clisp.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Stefan Liebler <stli@linux.ibm.com>, bug-gnulib@gnu.org
Subject: Re: FYI: s390x: Require GCC 7.1 or later to build glibc due to __builtin_add_overflow
Date: Fri, 18 Dec 2020 19:32:42 +0100	[thread overview]
Message-ID: <3477388.eNboq5l62f@omega> (raw)
In-Reply-To: <ee31d136-4a9d-a0e8-2333-5d6d7b29299c@cs.ucla.edu>

Paul Eggert wrote:
> > Thanks for the heads-up. Indeed, what I understand from this bug report is that
> > the condition code handling (required by __builtin_add_overflow on many
> > platforms) was unreliable before 2017-01-27, i.e. in GCC versions < 7.
> > So, gnulib shouldn't make use of it in these GCC versions.
> 
> So the problem is on all platforms, not just s390x?

That's my understanding, from the cited
<https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98269>.
Even if I'm wrong, given that GCC 5 and 6 are in decreasing use, I feel it's
better to err on the safe side.

Bruno



  reply	other threads:[~2020-12-18 18:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20201215141803.252050-1-stli@linux.ibm.com>
     [not found] ` <861d7df6-f87f-0ff6-5eda-9269a14d48f9@linaro.org>
2020-12-18  7:40   ` FYI: s390x: Require GCC 7.1 or later to build glibc due to __builtin_add_overflow Stefan Liebler
2020-12-18 12:14     ` Bruno Haible
2020-12-18 16:55       ` Paul Eggert
2020-12-18 18:32         ` Bruno Haible [this message]
2020-12-18 21:23           ` Paul Eggert
2021-01-07 17:00           ` Stefan Liebler

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

  List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3477388.eNboq5l62f@omega \
    --to=bruno@clisp.org \
    --cc=bug-gnulib@gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=stli@linux.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).