public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bouanto at zoho dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/114768] New: Volatile reads can be optimized away Date: Thu, 18 Apr 2024 13:19:52 +0000 [thread overview] Message-ID: <bug-114768-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114768 Bug ID: 114768 Summary: Volatile reads can be optimized away Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: rtl-optimization Assignee: unassigned at gcc dot gnu.org Reporter: bouanto at zoho dot com Target Milestone: --- In the following code: void test(int *ptr) { *ptr = *(volatile int *)ptr; } The volatile read is optimized away and GCC produces the following asm: test(int*): ret Godbolt link: https://gcc.godbolt.org/z/rabToGfqj Clang produces the following code: test(int*): # @test(int*) mov eax, dword ptr [rdi] ret which is likely to be the expected behavior.
next reply other threads:[~2024-04-18 13:19 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-18 13:19 bouanto at zoho dot com [this message] 2024-04-18 13:21 ` [Bug rtl-optimization/114768] " rguenth at gcc dot gnu.org 2024-04-18 13:21 ` jakub at gcc dot gnu.org 2024-04-18 13:23 ` rguenth at gcc dot gnu.org 2024-04-18 13:46 ` jakub at gcc dot gnu.org 2024-04-18 13:53 ` segher at gcc dot gnu.org 2024-04-18 13:57 ` segher at gcc dot gnu.org 2024-04-19 6:48 ` cvs-commit at gcc dot gnu.org 2024-04-19 6:49 ` jakub at gcc dot gnu.org 2024-04-19 10:38 ` cvs-commit at gcc dot gnu.org 2024-04-21 4:09 ` cvs-commit at gcc dot gnu.org 2024-04-23 6:43 ` jakub at gcc dot gnu.org 2024-06-11 10:38 ` cvs-commit at gcc dot gnu.org 2024-06-11 10:53 ` jakub 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-114768-4@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).