public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/99264] Ada doesn't build against latest glibc
Date: Thu, 25 Feb 2021 11:40:00 +0000	[thread overview]
Message-ID: <bug-99264-4-nx6um2zSjG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99264-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99264

--- Comment #5 from Florian Weimer <fw at gcc dot gnu.org> ---
(In reply to Eric Botcazou from comment #4)
> This looks like a serious compatibility breakage on the glibc side though.

POSIX does not require that the constant is usable in preprocessor macros, so
the code has always been invalid (technically speaking).

However, there is little that we can do. The hardware requirements have changed
under us, so even the kernel does not have much choice here. Applications
really have to adapt to the massively increased size of the register file,
there really is no way around that.

  parent reply	other threads:[~2021-02-25 11:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-25 10:02 [Bug ada/99264] New: " jakub at gcc dot gnu.org
2021-02-25 10:03 ` [Bug ada/99264] " jakub at gcc dot gnu.org
2021-02-25 10:07 ` rguenth at gcc dot gnu.org
2021-02-25 10:08 ` fw at gcc dot gnu.org
2021-02-25 10:10 ` fw at gcc dot gnu.org
2021-02-25 11:27 ` ebotcazou at gcc dot gnu.org
2021-02-25 11:40 ` fw at gcc dot gnu.org [this message]
2021-02-27  8:55 ` [Bug ada/99264] latest glibc release breaks Ada buildr on Linux ebotcazou at gcc dot gnu.org
2021-03-05 11:47 ` [Bug ada/99264] latest glibc release breaks Ada build " cvs-commit at gcc dot gnu.org
2021-03-05 11:53 ` cvs-commit at gcc dot gnu.org
2021-03-05 11:54 ` cvs-commit at gcc dot gnu.org
2021-03-05 11:56 ` ebotcazou at gcc dot gnu.org

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=bug-99264-4-nx6um2zSjG@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).