From: Paul Floyd <paulf@free.fr>
To: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: Safe transposition of logical and operands
Date: Tue, 19 Sep 2023 07:03:57 +0200 [thread overview]
Message-ID: <faf876a0-bcee-374f-131e-05c3875d7156@free.fr> (raw)
In-Reply-To: <36ac57c1e19b68fd588208a9ac03b58fe29fab32.camel@gwdg.de>
On 18-09-23 22:52, Martin Uecker wrote:
> Is the problem that valgrind transforms the code before it then
> emulates it and the problem is that during emulation the code
> could trap?
Yes, roughly the process is
guest ISA -> IR -> IR transformations -> IR optimizations -> execution
The && "idiom recovery" is getting filtered out during the IR
transformations.
A+
Paul
next prev parent reply other threads:[~2023-09-19 5:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-17 19:33 Paul Floyd
2023-09-17 20:51 ` Jonathan Wakely
2023-09-18 7:03 ` Paul Floyd
2023-09-18 7:23 ` Jonathan Wakely
2023-09-18 8:00 ` Richard Biener
2023-09-18 14:46 ` Floyd, Paul
2023-09-18 14:55 ` Richard Biener
2023-09-18 17:56 ` Paul Floyd
2023-09-18 19:09 ` Martin Uecker
2023-09-18 20:15 ` Paul Floyd
2023-09-18 20:52 ` Martin Uecker
2023-09-19 5:03 ` Paul Floyd [this message]
2023-09-18 9:36 ` Jonathan Wakely
2023-09-18 10:30 ` Andreas Schwab
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=faf876a0-bcee-374f-131e-05c3875d7156@free.fr \
--to=paulf@free.fr \
--cc=gcc@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).