public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "amonakov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/110052] useless local variable not optimized away Date: Thu, 01 Jun 2023 12:48:34 +0000 [thread overview] Message-ID: <bug-110052-4-9yDbzmW8JS@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110052-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110052 --- Comment #5 from Alexander Monakov <amonakov at gcc dot gnu.org> --- There are other reasons why it's invalid. For instance, in a multi-threaded program it could introduce a data race on assignment to foo->size inside of 'myrealloc' where the original program might have aborted without invoking UB. Can you give more context about the problem you're trying to solve?
prev parent reply other threads:[~2023-06-01 12:48 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-31 8:06 [Bug middle-end/110052] New: " aldot at gcc dot gnu.org 2023-05-31 8:31 ` [Bug middle-end/110052] " amonakov at gcc dot gnu.org 2023-05-31 8:51 ` rguenth at gcc dot gnu.org 2023-05-31 18:12 ` aldot at gcc dot gnu.org 2023-05-31 18:24 ` aldot at gcc dot gnu.org 2023-06-01 12:48 ` amonakov at gcc dot gnu.org [this message]
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-110052-4-9yDbzmW8JS@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).