public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/110369] wrong code on x86_64-linux-gnu Date: Thu, 22 Jun 2023 18:53:40 +0000 [thread overview] Message-ID: <bug-110369-4-uLG3E9lHEl@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110369-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110369 Marek Polacek <mpolacek at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mpolacek at gcc dot gnu.org --- Comment #1 from Marek Polacek <mpolacek at gcc dot gnu.org> --- I don't think it's wrong code: 110369.c:8:9: warning: iteration 2 invokes undefined behavior [-Waggressive-loop-optimizations] 8 | printf("%d", b[e]); | ^~~~~~~~~~~~~~~~~~ 110369.c:7:21: note: within this loop 7 | for (e = 0; e < 5; e++) { | ~~^~~ The behavior changed in r14-338.
next prev parent reply other threads:[~2023-06-22 18:53 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-22 18:36 [Bug tree-optimization/110369] New: " zhendong.su at inf dot ethz.ch 2023-06-22 18:53 ` mpolacek at gcc dot gnu.org [this message] 2023-06-22 18:57 ` [Bug tree-optimization/110369] " amonakov at gcc dot gnu.org 2023-06-22 19:00 ` [Bug tree-optimization/110369] [14 Regression] " mpolacek at gcc dot gnu.org 2023-06-22 21:01 ` [Bug rtl-optimization/110369] [14 Regression] wrong code on x86_64-linux-gnu with sel-scheduling pinskia at gcc dot gnu.org 2023-06-22 21:23 ` pinskia at gcc dot gnu.org 2024-03-04 4:56 ` law at gcc dot gnu.org 2024-05-07 7:40 ` [Bug rtl-optimization/110369] [14/15 " 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-110369-4-uLG3E9lHEl@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).