public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "georgmueller at gmx dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/108439] incorrect optimization with -O2, -O3, -Os Date: Tue, 17 Jan 2023 21:22:03 +0000 [thread overview] Message-ID: <bug-108439-4-FPQNnMndrE@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108439-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108439 --- Comment #1 from Georg Müller <georgmueller at gmx dot net> --- Created attachment 54293 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54293&action=edit reduced test case to give a compile warning, which seems to be incorrect While trying to reduce the problem and reducing the array size of lb_key to ony one member (t_crap8-1u64.c), it gives a compile error with -O2, -O3 and -Os even if the only member gets initialized all the time with the line "lb_key[0] = 0x1234;". Also, this compiler warning and execution error is removed by compiling with -fno-strict-aliasing, but again, this does not look right.
next prev parent reply other threads:[~2023-01-17 21:22 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-17 21:17 [Bug c/108439] New: " georgmueller at gmx dot net 2023-01-17 21:22 ` georgmueller at gmx dot net [this message] 2023-01-17 21:25 ` [Bug c/108439] " georgmueller at gmx dot net 2023-01-17 21:32 ` pinskia at gcc dot gnu.org 2023-01-17 21:33 ` pinskia at gcc dot gnu.org 2023-01-17 21:44 ` georgmueller at gmx dot net 2023-01-17 21:51 ` pinskia at gcc dot gnu.org 2023-01-18 9:01 ` georgmueller at gmx dot net
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-108439-4-FPQNnMndrE@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).