public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/63359] aarch64: 32bit registers in inline asm
Date: Wed, 24 Sep 2014 15:21:00 -0000	[thread overview]
Message-ID: <bug-63359-4-KGUeDdskpC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63359-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #8 from Richard Earnshaw <rearnsha at gcc dot gnu.org> ---
(In reply to James Molloy from comment #6)
> Good example, although I might argue slightly pathological.
> 

Agreed, this is somewhat pathological, but I only need to find one valid
counter-example :-)

Furthermore, something similar will be quite common on results.  Eg:

int i, j;
unsigned long r;
asm("add %w0, %w1, %w2" : "=r"(r) : "r"(i), "r"(j));  // zero-extend result.

here we *want* the 64-bit result from the implicit zero-extend of writing the
lower 32 bits.

> So in this case currently, GCC doesn't even implicitly promote the argument,
> just uses it as-is. It seems a very dangerous behaviour to have as default.
> Could there not be a more sensible default and an explicit constraint
> modifier to allow this instead?

One of the things I dislike so much about GCC's inline assembly is that it's
just an exposure to users of an internal API in the compiler.  That makes it
very difficult to say precisely what will happen in all cases and *very* hard
to fix problems with it when it exposes bugs.

I'm not saying I'll never accept a warning for this sort of code; but I'd need
convincing that it won't unduly pessimize real code with no acceptable
work-arounds.


  parent reply	other threads:[~2014-09-24 15:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-24 13:26 [Bug target/63359] New: " glisse at gcc dot gnu.org
2014-09-24 13:55 ` [Bug target/63359] " james.molloy at arm dot com
2014-09-24 14:44 ` rearnsha at gcc dot gnu.org
2014-09-24 14:47 ` james.molloy at arm dot com
2014-09-24 14:57 ` rearnsha at gcc dot gnu.org
2014-09-24 15:04 ` james.molloy at arm dot com
2014-09-24 15:07 ` glisse at gcc dot gnu.org
2014-09-24 15:21 ` rearnsha at gcc dot gnu.org [this message]
2014-09-24 15:27 ` james.molloy at arm dot com
2020-06-15 11:07 ` andysem at mail dot ru

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-63359-4-KGUeDdskpC@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).