From: Andrew Haley <aph@redhat.com>
To: gcc-help@gcc.gnu.org
Subject: Re: gcc-trunk generates incorrect code for LEA in asm template
Date: Sat, 15 Jul 2023 10:28:07 +0100 [thread overview]
Message-ID: <4ba30c6e-59dd-3f28-40b7-53a45aea84b5@redhat.com> (raw)
In-Reply-To: <f68d0903-9b9b-9918-3ff7-e70b9d12c0e1@free.fr>
On 7/15/23 01:40, Mason via Gcc-help wrote:
> Why though?
The asm as here has no effect. You need a memory clobber.
--
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
prev parent reply other threads:[~2023-07-15 9:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-14 18:18 Mason
2023-07-15 0:40 ` Mason
2023-07-15 9:28 ` Andrew Haley [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=4ba30c6e-59dd-3f28-40b7-53a45aea84b5@redhat.com \
--to=aph@redhat.com \
--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).