This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] Don't cross-jump in between frame related and non-frame related insns (PR target/80102)
- From: Richard Henderson <rth at redhat dot com>
- To: Jakub Jelinek <jakub at redhat dot com>, gcc-patches at gcc dot gnu dot org
- Date: Tue, 21 Mar 2017 08:38:20 +1000
- Subject: Re: [PATCH] Don't cross-jump in between frame related and non-frame related insns (PR target/80102)
- Authentication-results: sourceware.org; auth=none
- References: <20170320211520.GO11094@tucnak>
On 03/21/2017 07:15 AM, Jakub Jelinek wrote:
Not really sure what we should do if both i1 and i2 are frame related, shall
we check for each of the CFA reg notes if they are available and equal?
Or punt if either of the insns is frame related?
I would punt if either is frame related.
As an aside, if the length of "blockage" is corrected to 0, does cross-jumping
skip this case? Because replacing a simple_return with a direct branch to a
simple_return is not a win. But of course at the moment cross-jumping thinks
it is eliminating the second blockage as well...
r~