public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "eggert at cs dot ucla.edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/101913] -Wstrict-overflow -O3 false alarm on tzdb localtime.c Date: Sat, 14 Aug 2021 22:22:03 +0000 [thread overview] Message-ID: <bug-101913-4-fTvunBPzH9@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101913-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101913 eggert at cs dot ucla.edu changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #51304|0 |1 is obsolete| | --- Comment #2 from eggert at cs dot ucla.edu --- Created attachment 51305 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51305&action=edit -Wstrict-overflow -O3 false alarm example (v2) This updates the example by replacing -1L<<63 with -1-9223372036854775807L, to avoid any undefined behavior in evaluating that constant expression.
next prev parent reply other threads:[~2021-08-14 22:22 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-14 20:19 [Bug c/101913] New: " eggert at cs dot ucla.edu 2021-08-14 20:31 ` [Bug middle-end/101913] " pinskia at gcc dot gnu.org 2021-08-14 22:22 ` eggert at cs dot ucla.edu [this message] 2021-08-14 22:30 ` eggert at cs dot ucla.edu 2021-12-23 5:24 ` pinskia at gcc dot gnu.org 2022-01-31 16:25 ` marxin 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-101913-4-fTvunBPzH9@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).