public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/107493] [13 Regression] Wrong code at -Os on x86_64-linux-gnu Date: Tue, 01 Nov 2022 15:27:31 +0000 [thread overview] Message-ID: <bug-107493-4-ISGua3AmOi@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107493-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107493 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |needs-bisection --- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> --- self contained testcase: int a; int b(int c) { return c; } int main() { a = -21; for (; a <= 0; a = (unsigned short)(b(a + 2) + 8)) ; if (a != 65525) __builtin_abort(); // __builtin_printf("%d\n", a); }
next prev parent reply other threads:[~2022-11-01 15:27 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-01 11:49 [Bug c/107493] New: " shaohua.li at inf dot ethz.ch 2022-11-01 15:25 ` [Bug tree-optimization/107493] [13 Regression] " pinskia at gcc dot gnu.org 2022-11-01 15:27 ` pinskia at gcc dot gnu.org [this message] 2022-11-05 10:37 ` rguenth at gcc dot gnu.org 2022-11-08 13:29 ` rguenth at gcc dot gnu.org 2022-11-21 12:17 ` [Bug tree-optimization/107493] [13 Regression] Wrong code at -Os on x86_64-linux-gnu since r13-3486-g4c5b116077638277 marxin at gcc dot gnu.org 2022-11-22 8:09 ` rguenth at gcc dot gnu.org 2022-11-28 10:17 ` cvs-commit at gcc dot gnu.org 2022-11-28 10:18 ` rguenth 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-107493-4-ISGua3AmOi@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).