From: Andrew Haley <aph@redhat.com>
To: Joe Buehler <aspam@cox.net>, gcc-help@gcc.gnu.org
Subject: Re: aarch64 inline asm / -fPIC problem
Date: Sat, 29 Aug 2020 16:45:08 +0100 [thread overview]
Message-ID: <8dff32c6-4e2c-2a1a-4216-98951f52b552@redhat.com> (raw)
In-Reply-To: <5F48246C.6040402@cox.net>
On 27/08/2020 22:23, Joe Buehler via Gcc-help wrote:
temp.c: In function main :
temp.c:4:2: warning: asm operand 0 probably doesn t match constraints
__asm__ volatile(".8byte %0\n\t" : : "i" ("message %s\n"));
^~~~~~~
temp.c:4:2: error: impossible constraint in asm
I'd use the "S" constraint.
> I am unable to code something similar manually using inline asm because
> the string is a format string containing % characters, which inline asm
> will of course try to interpret. (Does gcc provide anything to escape %
> chars in a literal string?)
"%%"
--
Andrew Haley (he/him)
Java Platform Lead Engineer
Red Hat UK Ltd. <https://www.redhat.com>
https://keybase.io/andrewhaley
EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671
next prev parent reply other threads:[~2020-08-29 15:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-27 21:23 Joe Buehler
2020-08-28 13:45 ` Joe Buehler
2020-08-28 15:17 ` Joe Buehler
2020-08-29 15:45 ` Andrew Haley [this message]
2020-09-02 18:25 ` aph@redhat.com Joe Buehler
2020-09-03 10:18 ` aph@redhat.com Andrew Haley
2020-09-02 18:26 ` aarch64 inline asm / -fPIC problem Joe Buehler
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=8dff32c6-4e2c-2a1a-4216-98951f52b552@redhat.com \
--to=aph@redhat.com \
--cc=aspam@cox.net \
--cc=gcc-help@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).