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 rtl-optimization/103979] asm goto is not considered volatile with output operands Date: Mon, 30 Jan 2023 18:06:59 +0000 [thread overview] Message-ID: <bug-103979-4-Qoj50zk4Fq@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103979-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103979 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> --- struct S { char a[64]; }; int foo (void) { struct S s, t; asm goto ("" : "=g" (s) : : : l); t = s; asm goto ("" : "=g" (s) : : : l); return s.a[0] + t.a[63]; l: return -1; } also ICEs at -O2, not during fwprop (note, I can't reproduce the #c0 testcase, neither with trunk nor 11 branch on x86_64-linux), but during sra. I think we shouldn't just follow blindly the docs, but see what e.g. Linux kernel as heavy user of asm goto with outputs (and I think mostly without volatile) wants.
next prev parent reply other threads:[~2023-01-30 18:06 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-11 16:29 [Bug c/103979] New: asm goto is not considered volatile gareth.webb+gccbugzilla at outlook dot com 2022-01-11 18:46 ` [Bug rtl-optimization/103979] asm goto is not considered volatile with output operands pinskia at gcc dot gnu.org 2023-01-25 22:17 ` pinskia at gcc dot gnu.org 2023-01-30 18:06 ` jakub at gcc dot gnu.org [this message] 2023-01-30 18:18 ` jakub at gcc dot gnu.org 2023-06-26 23:38 ` [Bug middle-end/103979] " pinskia at gcc dot gnu.org 2023-06-26 23:53 ` pinskia at gcc dot gnu.org 2023-06-27 0:10 ` pinskia at gcc dot gnu.org 2023-06-27 3:26 ` pinskia at gcc dot gnu.org 2023-06-27 16:28 ` cvs-commit at gcc dot gnu.org 2023-06-27 16:29 ` pinskia at gcc dot gnu.org 2023-06-27 16:46 ` cvs-commit at gcc dot gnu.org 2023-06-27 17:21 ` cvs-commit at gcc dot gnu.org 2023-06-27 17:24 ` pinskia 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-103979-4-Qoj50zk4Fq@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).