From: Andreas Schwab <schwab@suse.de>
To: Paul Floyd via Gcc <gcc@gcc.gnu.org>
Cc: Paul Floyd <paulf@free.fr>
Subject: Re: Safe transposition of logical and operands
Date: Mon, 18 Sep 2023 12:30:35 +0200 [thread overview]
Message-ID: <mvmedivvkms.fsf@suse.de> (raw)
In-Reply-To: <12c6db0e-10cf-eef6-6209-77da64738897@free.fr> (Paul Floyd via Gcc's message of "Sun, 17 Sep 2023 21:33:21 +0200")
On Sep 17 2023, Paul Floyd via Gcc wrote:
> However, Valgrind thinks that these transpositions can't be done when
> there are potentially trapping memory loads like *f.
*f is not doing any pointer dereference. It just reads the _M_payload
member of f.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
prev parent reply other threads:[~2023-09-18 10:30 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
2023-09-18 9:36 ` Jonathan Wakely
2023-09-18 10:30 ` Andreas Schwab [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=mvmedivvkms.fsf@suse.de \
--to=schwab@suse.de \
--cc=gcc@gcc.gnu.org \
--cc=paulf@free.fr \
/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).