public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "daniel.lundin.mail at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/108295] Free label positions shouldn't be available outside -std=c2x
Date: Thu, 05 Jan 2023 09:42:06 +0000	[thread overview]
Message-ID: <bug-108295-4-Mqcrcvkv4O@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108295-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #9 from Daniel Lundin <daniel.lundin.mail at gmail dot com> ---
(In reply to Andrew Pinski from comment #8)
> "When a base standard is specified, the compiler accepts all programs
> following that standard plus those using GNU extensions that do not
> contradict it."
> 
> Wrong again.
> https://gcc.gnu.org/onlinedocs/gcc-12.2.0/gcc/C-Dialect-Options.html#index-
> std-1

In this case the GNU extension does contradict the ISO 9899:2018 standard. A
conforming compiler is required to issue a diagnostic (as per 5.1.1.3) upon
spotting a violation of the syntax in 6.8.1.

  parent reply	other threads:[~2023-01-05  9:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-05  8:36 [Bug c/108295] New: " daniel.lundin.mail at gmail dot com
2023-01-05  8:42 ` [Bug c/108295] " daniel.lundin.mail at gmail dot com
2023-01-05  8:53 ` schwab@linux-m68k.org
2023-01-05  8:55 ` daniel.lundin.mail at gmail dot com
2023-01-05  9:00 ` pinskia at gcc dot gnu.org
2023-01-05  9:18 ` daniel.lundin.mail at gmail dot com
2023-01-05  9:27 ` pinskia at gcc dot gnu.org
2023-01-05  9:31 ` daniel.lundin.mail at gmail dot com
2023-01-05  9:35 ` pinskia at gcc dot gnu.org
2023-01-05  9:42 ` daniel.lundin.mail at gmail dot com [this message]
2023-01-05  9:50 ` pinskia at gcc dot gnu.org
2023-01-05  9:54 ` jakub at gcc dot gnu.org
2023-01-05  9:55 ` pinskia 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-108295-4-Mqcrcvkv4O@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).