public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ibuclaw at gdcproject dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug d/94425] [D] Consider always settings ASM_VOLATILE_P on asm statements
Date: Wed, 01 Apr 2020 17:38:55 +0000	[thread overview]
Message-ID: <bug-94425-4-kKBoCLLQiG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94425-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Iain Buclaw <ibuclaw at gdcproject dot org> ---
(In reply to Richard Biener from comment #1)
> Well, there's no dependence visible to the compiler between the control word
> stores and loads so it's obvious the asms cannot be pure.  Is 'asm' a D
> feature or a GCC extension?  How does D model dependences between asms?

It should be considered a feature, though the spec is ignored for the sake of
both convenience and portability.

As far as the semantic analyzer treats them, they are just black holes assumed
to do anything.

The reference compiler (DMD) even goes as far as refusing to inline functions
with that contain any asm statements.  That could be another solution, but
allow overriding with pragma(inline).

  parent reply	other threads:[~2020-04-01 17:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-31 14:46 [Bug d/94425] New: " ibuclaw at gdcproject dot org
2020-04-01  6:59 ` [Bug d/94425] " rguenth at gcc dot gnu.org
2020-04-01 17:38 ` ibuclaw at gdcproject dot org [this message]
2020-04-06 13:27 ` ibuclaw at gdcproject dot org
2020-04-07  7:44 ` cvs-commit at gcc dot gnu.org
2020-04-07 16:32 ` ibuclaw at gdcproject dot 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-94425-4-kKBoCLLQiG@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).