public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/110664] New: -std=c2x -pedantic-errors pedwarns on _Float128 Date: Fri, 14 Jul 2023 11:09:33 +0000 [thread overview] Message-ID: <bug-110664-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110664 Bug ID: 110664 Summary: -std=c2x -pedantic-errors pedwarns on _Float128 Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: jakub at gcc dot gnu.org Target Milestone: --- _Float128 f = 1.0F128; gcc -S -std=c2x -o /dev/null test.c -pedantic-errors test.c:1:1: error: ISO C does not support the ‘_Float128’ type [-Wpedantic] 1 | _Float128 f = 1.0F128; | ^~~~~~~~~ test.c:1:1: error: non-standard suffix on floating constant [-Wpedantic] doesn't seem right to me, shouldn't those pedwarns be skipped for flag_isoc2x?
next reply other threads:[~2023-07-14 11:09 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-14 11:09 jakub at gcc dot gnu.org [this message] 2023-07-20 23:16 ` [Bug c/110664] " joseph at codesourcery dot com 2023-07-20 23:47 ` pinskia at gcc dot gnu.org 2023-09-06 14:56 ` jsm28 at gcc dot gnu.org 2023-09-06 15:16 ` jakub 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-110664-4@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: linkBe 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).