public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "alexhenrie24 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/66618] Failure to diagnose non-constant initializer for static object with -O1
Date: Mon, 22 May 2023 19:11:22 +0000 [thread overview]
Message-ID: <bug-66618-4-UPCdwNDJDX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66618-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66618
--- Comment #9 from Alex Henrie <alexhenrie24 at gmail dot com> ---
(In reply to Andrew Pinski from comment #7)
> (In reply to Alex Henrie from comment #6)
> > This wasn't fixed properly, or it was broken again before the release of GCC
> > 8.1: In GCC 8.1 and later no warning at all is issued for the example
> > program, even at -O0.
>
> The fix was to change it to be a valid constant expression ....
Oh, okay. When I read Comment 2 I thought that a -Wpedantic warning was
intended. If the intention was to have no warning ever then everything is fine.
prev parent reply other threads:[~2023-05-22 19:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-21 21:09 [Bug c/66618] New: " Keith.S.Thompson at gmail dot com
2015-06-22 12:58 ` [Bug c/66618] " mpolacek at gcc dot gnu.org
2015-06-22 13:46 ` joseph at codesourcery dot com
2015-07-01 0:48 ` Keith.S.Thompson at gmail dot com
2023-05-22 18:57 ` alexhenrie24 at gmail dot com
2023-05-22 19:04 ` pinskia at gcc dot gnu.org
2023-05-22 19:04 ` pinskia at gcc dot gnu.org
2023-05-22 19:11 ` alexhenrie24 at gmail dot com [this message]
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-66618-4-UPCdwNDJDX@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).