From: Alexandre Oliva <oliva@adacore.com>
To: Richard Biener <richard.guenther@gmail.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] [strub] improve handling of indirected volatile parms [PR112938]
Date: Tue, 16 Apr 2024 00:55:21 -0300 [thread overview]
Message-ID: <orbk6ac66u.fsf@lxoliva.fsfla.org> (raw)
In-Reply-To: <CAFiYyc0Z7MKGaUSHv92xw99ko+=DPWJ4S2yZRYS9XR5rGZm-og@mail.gmail.com> (Richard Biener's message of "Mon, 11 Mar 2024 08:26:27 +0100")
On Mar 11, 2024, Richard Biener <richard.guenther@gmail.com> wrote:
> On Sat, Mar 9, 2024 at 10:10 AM Alexandre Oliva <oliva@adacore.com> wrote:
>>
>>
>> The earlier patch for PR112938 arranged for volatile parms to be made
>> indirect in internal strub wrapped bodies.
>>
>> The first problem that remained, more evident, was that the indirected
>> parameter remained volatile, despite the indirection, but it wasn't
>> regimplified, so indirecting it was malformed gimple.
>>
>> Regimplifying turned out not to be needed. The best course of action
>> was to drop the volatility from the by-reference parm, that was being
>> unexpectedly inherited from the original volatile parm.
>>
>> That exposed another problem: the dereferences would then lose their
>> volatile status, so we had to bring volatile back to them.
>>
>> Regstrapped on x86_64-linux-gnu. Ok to install?
> OK
Thanks, sorry, I dropped the ball on this one.
I'm going to put it in momentarily. It had been approved for gcc 14,
before it branched off; should I install it there as well?
>>
>> for gcc/ChangeLog
>>
>> PR middle-end/112938
>> * ipa-strub.cc (pass_ipa_strub::execute): Drop volatility from
>> indirected parm.
>> (maybe_make_indirect): Restore volatility in dereferences.
>>
>> for gcc/testsuite/ChangeLog
>>
>> PR middle-end/112938
>> * g++.dg/strub-internal-pr112938.cc: New.
--
Alexandre Oliva, happy hacker https://FSFLA.org/blogs/lxo/
Free Software Activist GNU Toolchain Engineer
More tolerance and less prejudice are key for inclusion and diversity
Excluding neuro-others for not behaving ""normal"" is *not* inclusive
next prev parent reply other threads:[~2024-04-16 3:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-09 9:09 Alexandre Oliva
2024-03-11 7:26 ` Richard Biener
2024-04-16 3:55 ` Alexandre Oliva [this message]
2024-04-16 5:29 ` Alexandre Oliva
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=orbk6ac66u.fsf@lxoliva.fsfla.org \
--to=oliva@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.guenther@gmail.com \
/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).