From: "Arsen Arsenović" <arsen@aarsen.me>
To: Florian Weimer <fweimer@redhat.com>, gcc-patches@gcc.gnu.org
Cc: gcc@gcc.gnu.org, Joseph Myers <joseph@codesourcery.com>,
Marek Polacek <polacek@redhat.com>
Subject: Re: C2x features status
Date: Fri, 21 Oct 2022 21:29:24 +0200 [thread overview]
Message-ID: <7452271.dsUahkEHV4@bstg> (raw)
In-Reply-To: <Y1LvrsozecvovW91@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 841 bytes --]
On Friday, 21 October 2022 21:14:54 CEST Marek Polacek via Gcc wrote:
> commit 0a91bdaf177409a2a5e7895bce4f0e7091b4b3ca
> Author: Joseph Myers <joseph@codesourcery.com>
> Date: Wed Sep 7 13:56:25 2022 +0000
>
> c: New C2x keywords
>
> which says:
>
> As with the removal of unprototyped functions, this change has a
> high risk of breaking some old code and people doing GNU/Linux
> distribution builds may wish to see how much is broken in a build
> with a -std=gnu2x default.
It already does break a lot. See https://bugs.gentoo.org/870412
(comments go over the details). I was intending on giving this issue a
proper look in the GNU toolchain frame of reference, but never got
around to it (and I kinda knocked priority down after managing to
configure properly once IIRC).
--
Arsen Arsenović
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 358 bytes --]
next prev parent reply other threads:[~2022-10-21 20:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 17:30 Joseph Myers
2022-10-21 18:31 ` Florian Weimer
2022-10-21 19:14 ` Marek Polacek
2022-10-21 19:29 ` Arsen Arsenović [this message]
2022-10-21 19:55 ` Florian Weimer
2022-10-21 20:26 ` Arsen Arsenović
2022-10-21 21:11 ` Joseph Myers
2022-10-21 22:13 ` Florian Weimer
2022-10-21 22:19 ` Joseph Myers
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=7452271.dsUahkEHV4@bstg \
--to=arsen@aarsen.me \
--cc=fweimer@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=joseph@codesourcery.com \
--cc=polacek@redhat.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).