From: Alexander Monakov <amonakov@ispras.ru>
To: Uros Bizjak <ubizjak@gmail.com>
Cc: Richard Biener <richard.guenther@gmail.com>,
Jakub Jelinek <jakub@redhat.com>,
GCC Development <gcc@gcc.gnu.org>, X86 ML <x86@kernel.org>,
Andy Lutomirski <luto@amacapital.net>
Subject: Re: typeof and operands in named address spaces
Date: Thu, 5 Nov 2020 16:22:43 +0300 (MSK) [thread overview]
Message-ID: <alpine.LNX.2.20.13.2011051612130.9902@monopod.intra.ispras.ru> (raw)
In-Reply-To: <CAFULd4ZHcfsK=H4OTqeYS+N+9y=sr=DuJ0TN4JYBCk5_G6gMRA@mail.gmail.com>
On Thu, 5 Nov 2020, Uros Bizjak via Gcc wrote:
> > No, this is not how LEA operates. It needs a memory input operand. The
> > above will report "operand type mismatch for 'lea'" error.
>
> The following will work:
>
> asm volatile ("lea (%1), %0" : "=r"(addr) : "r"((uintptr_t)&x));
This is the same as a plain move though, and the cast to uintptr_t doesn't
do anything, you can simply pass "r"(&x) to the same effect.
The main advantage of passing a "fake" memory location for use with lea is
avoiding base+offset computation outside the asm. If you're okay with one
extra register tied up by the asm, just pass the address to the asm directly:
void foo(__seg_fs int *x)
{
asm("# %0 (%1)" :: "m"(x[1]), "r"(&x[1]));
asm("# %0 (%1)" :: "m"(x[0]), "r"(&x[0]));
}
foo:
leaq 4(%rdi), %rax
# %fs:4(%rdi) (%rax)
# %fs:(%rdi) (%rdi)
ret
Alexander
next prev parent reply other threads:[~2020-11-05 13:22 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-04 18:31 Uros Bizjak
2020-11-05 7:26 ` Richard Biener
2020-11-05 8:56 ` Uros Bizjak
2020-11-05 9:36 ` Alexander Monakov
2020-11-05 10:33 ` Uros Bizjak
2020-11-05 11:38 ` Alexander Monakov
2020-11-05 12:00 ` Uros Bizjak
2020-11-05 12:14 ` Alexander Monakov
2020-11-05 12:24 ` Richard Biener
2020-11-05 12:32 ` Uros Bizjak
2020-11-05 12:35 ` Uros Bizjak
2020-11-05 13:22 ` Alexander Monakov [this message]
2020-11-05 13:39 ` Alexander Monakov
2020-11-05 13:46 ` Uros Bizjak
2020-11-05 12:26 ` Uros Bizjak
2020-11-05 15:27 ` Andy Lutomirski
2020-11-05 11:03 ` Uros Bizjak
2020-11-05 9:45 ` Richard Biener
2020-11-05 9:51 ` Jakub Jelinek
2020-11-09 12:47 ` Peter Zijlstra
2020-11-09 19:38 ` Segher Boessenkool
2020-11-09 19:50 ` Nick Desaulniers
2020-11-10 7:57 ` Peter Zijlstra
2020-11-10 18:42 ` Nick Desaulniers
2020-11-10 20:11 ` Peter Zijlstra
2020-11-12 0:40 ` Segher Boessenkool
2020-11-12 0:47 ` Segher Boessenkool
2020-11-10 7:52 ` Peter Zijlstra
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=alpine.LNX.2.20.13.2011051612130.9902@monopod.intra.ispras.ru \
--to=amonakov@ispras.ru \
--cc=gcc@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=luto@amacapital.net \
--cc=richard.guenther@gmail.com \
--cc=ubizjak@gmail.com \
--cc=x86@kernel.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).