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 middle-end/108712] Missing optimization with memory-barrier Date: Wed, 08 Feb 2023 19:41:41 +0000 [thread overview] Message-ID: <bug-108712-4-ShQhTwinZF@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108712-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108712 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |inline-asm, | |missed-optimization --- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> --- The inline-asm is causing GCC not to optimize the code. Doing the following on x86_64 allows GCC to optimize the g load/stores out of the loop: static volatile int flag; static int g; void func(void) { for(int i = 0; i < 20; i++) { ++g; if (flag) { flag = 0; } } }
prev parent reply other threads:[~2023-02-08 19:41 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-08 8:33 [Bug c/108712] New: " klaus.doldinger64 at googlemail dot com 2023-02-08 8:43 ` [Bug middle-end/108712] " klaus.doldinger64 at googlemail dot com 2023-02-08 19:41 ` pinskia 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-108712-4-ShQhTwinZF@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).