From: Jeff Law <law@redhat.com>
To: Wilco Dijkstra <Wilco.Dijkstra@arm.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Cc: nd <nd@arm.com>
Subject: Re: [PATCH v2] Fix PR64242
Date: Fri, 31 May 2019 21:41:00 -0000 [thread overview]
Message-ID: <bf754387-6afe-0ff4-8fd5-1c2a3bb36785@redhat.com> (raw)
In-Reply-To: <VI1PR0801MB2127E401872D3A419F90367F831E0@VI1PR0801MB2127.eurprd08.prod.outlook.com>
On 5/28/19 11:26 AM, Wilco Dijkstra wrote:
> Improve the fix for PR64242. Various optimizations can change a memory reference
> into a frame access. Given there are multiple virtual frame pointers which may
> be replaced by multiple hard frame pointers, there are no checks for writes to the
> various frame pointers. So updates to a frame pointer tends to generate incorrect
> code. Improve the previous fix to also add clobbers of several frame pointers and
> add a scheduling barrier. This should work in most cases until GCC supports a
> generic "don't optimize across this instruction" feature.
>
> Bootstrap OK. Testcase passes on AArch64 and x86-64. Inspected x86, Arm,
> Thumb-1 and Thumb-2 assembler which looks correct.
>
> ChangeLog:
> 2018-12-07 Wilco Dijkstra <wdijkstr@arm.com>
>
> gcc/
> PR middle-end/64242
> * builtins.c (expand_builtin_longjmp): Add frame clobbers and schedule block.
> (expand_builtin_nonlocal_goto): Likewise.
>
> testsuite/
> PR middle-end/64242
> * gcc.c-torture/execute/pr64242.c: Update test.
OK. Though given history we might expect some targets to barf on the
test changes. Please keep an eye out for such breakage.
jeff
next prev parent reply other threads:[~2019-05-31 21:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-28 17:33 Wilco Dijkstra
2019-05-31 21:41 ` Jeff Law [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-12-07 14:52 Wilco Dijkstra
2018-12-07 15:55 ` Jakub Jelinek
2018-12-07 16:19 ` Wilco Dijkstra
2018-12-07 16:23 ` Jakub Jelinek
2018-12-07 16:49 ` Wilco Dijkstra
2019-01-10 13:06 ` Wilco Dijkstra
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=bf754387-6afe-0ff4-8fd5-1c2a3bb36785@redhat.com \
--to=law@redhat.com \
--cc=Wilco.Dijkstra@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=nd@arm.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).