public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug inline-asm/102150] Speculative execution of inline assembly causes divide error
Date: Wed, 01 Sep 2021 08:41:21 +0000	[thread overview]
Message-ID: <bug-102150-4-Z13SBwHJBr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102150-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102150

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |rguenth at gcc dot gnu.org

--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
We have

bool
gimple_could_trap_p_1 (const gimple *s, bool include_mem, bool include_stores)
{
...
    case GIMPLE_ASM:
      return gimple_asm_volatile_p (as_a <const gasm *> (s));

so we consider ASMs not trapping unless they are volatile.  Note we do
check the asm operands for possible traps, for example if memory inputs
or outputs are a possible source of traps that doesn't need the ASM to be
marked volatile.

And yes, we'd require the ASM to be not trapping even when not executed
on the actual input.

      reply	other threads:[~2021-09-01  8:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-01  0:56 [Bug rtl-optimization/102150] New: " jeremy-gcc-bugzilla at sawicki dot us
2021-09-01  8:41 ` rguenth 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-102150-4-Z13SBwHJBr@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).