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/108684] [12/13 Regression] ICE: verify_ssa failed
Date: Tue, 07 Feb 2023 19:59:19 +0000 [thread overview]
Message-ID: <bug-108684-4-fWP2DPNULU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108684-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108684
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #9 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #8)
> I think simple_dce_from_worklist is incorrect of removing this inline-asm in
> the first place.
> Take:
> ```
> static int t;
>
> int f (int *a)
> {
> int t1;
> asm (" " : "=r" (t1) : : "memory");
> t = t1;
> return *a;
> }
> ```
> The inline-asm could have written to *a but now it has been removed.
I think that is how inline asm always behaved. If it is not ok to be DCEd when
the result is dead, one needs to use volatile keyword.
next prev parent reply other threads:[~2023-02-07 19:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-06 18:49 [Bug c++/108684] New: [13 " gscfq@t-online.de
2023-02-06 18:55 ` [Bug tree-optimization/108684] " pinskia at gcc dot gnu.org
2023-02-06 20:23 ` pinskia at gcc dot gnu.org
2023-02-06 20:26 ` pinskia at gcc dot gnu.org
2023-02-07 14:05 ` rguenth at gcc dot gnu.org
2023-02-07 18:30 ` amacleod at redhat dot com
2023-02-07 18:33 ` pinskia at gcc dot gnu.org
2023-02-07 18:37 ` [Bug tree-optimization/108684] [12/13 " pinskia at gcc dot gnu.org
2023-02-07 18:39 ` amacleod at redhat dot com
2023-02-07 18:45 ` pinskia at gcc dot gnu.org
2023-02-07 19:56 ` pinskia at gcc dot gnu.org
2023-02-07 19:59 ` jakub at gcc dot gnu.org [this message]
2023-02-07 20:03 ` pinskia at gcc dot gnu.org
2023-02-08 19:14 ` pinskia at gcc dot gnu.org
2023-02-09 15:23 ` pinskia at gcc dot gnu.org
2023-02-10 1:47 ` cvs-commit at gcc dot gnu.org
2023-02-10 1:48 ` [Bug tree-optimization/108684] [12 " pinskia at gcc dot gnu.org
2023-03-10 21:55 ` cvs-commit at gcc dot gnu.org
2023-03-10 21:55 ` pinskia at gcc dot gnu.org
2023-05-13 14:17 ` 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-108684-4-fWP2DPNULU@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: link
Be 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).