public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/102769] wrong code at -O1 and above on x86_64-linux-gnu Date: Fri, 15 Oct 2021 10:23:14 +0000 [thread overview] Message-ID: <bug-102769-4-HqgZ3jT6JN@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102769-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102769 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> --- It is still UB, the b = &h; happens inside of the scope, then the scope is left and on a next iteration rentered again and *b dereferenced. I don't think C/C++ have anything that would special case {}s around body of the loop, though in most versions of the languages there is an extra for scope around it.
next prev parent reply other threads:[~2021-10-15 10:23 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-15 9:36 [Bug tree-optimization/102769] New: " zhendong.su at inf dot ethz.ch 2021-10-15 9:47 ` [Bug tree-optimization/102769] " marxin at gcc dot gnu.org 2021-10-15 10:19 ` zhendong.su at inf dot ethz.ch 2021-10-15 10:23 ` jakub at gcc dot gnu.org [this message] 2021-10-15 10:23 ` marxin at gcc dot gnu.org 2021-10-15 10:28 ` zhendong.su at inf dot ethz.ch 2021-10-15 10:33 ` marxin at gcc dot gnu.org 2021-10-15 10:38 ` zhendong.su at inf dot ethz.ch 2021-10-15 10:43 ` marxin at gcc dot gnu.org 2021-10-15 11:39 ` zhendong.su at inf dot ethz.ch 2021-10-15 11:42 ` jakub at gcc dot gnu.org 2021-10-15 15:17 ` zhendong.su at inf dot ethz.ch
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-102769-4-HqgZ3jT6JN@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).