From: Jeff Law <law@redhat.com>
To: Bernd Schmidt <bernds@codesourcery.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: RFA PR middle-end/48770
Date: Tue, 31 May 2011 18:33:00 -0000 [thread overview]
Message-ID: <4DE529A5.2070902@redhat.com> (raw)
In-Reply-To: <4DE377B9.1060303@codesourcery.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 05/30/11 04:55, Bernd Schmidt wrote:
> On 05/27/2011 07:49 PM, Jeff Law wrote:
>> Updated based on some comments from Bernd; specifically the other use of
>> delete_dead_insn has been removed.
>>
>> WRT the assembly differences on MIPS Bernd referred to; what ultimately
>> caused this problem were two dead insns that had been previously
>> eliminated by reload were still in the insn stream and inhibited an
>> if-conversion which resulted in slightly different assembly code, but
>> shouldn't have had any significant impact on the performance or size of
>> the resulting code. The dead insns were deleted by the post-reload DCE
>> pass (which obviously runs after post-reload if conversion).
>>
>> If we really wanted to get those insns out of the stream, we could flag
>> when reload deleted insns which might result in dead code remaining in
>> the stream, then conditionally run DCE immediately after reload. I
>> didn't think this was worth doing right now, but if someone objects I
>> can certainly look into it.
>
> Patch is OK (still no codegen changes on x86 as far as I can tell), but
> I'd appreciate the DCE thing as a followup.
I suspect it's going to be just as easy to go ahead and add the DCE
cleanup now rather than waiting. It should be a relatively trivial
tweak to delete_dead_insn to set a flag which we'd check at the end of
reload. It's #2 in the queue :-)
jeff
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJN5SmlAAoJEBRtltQi2kC7RfwH/RV9OsQIwMeKOHUOgOkpvQZx
DIjRjlGTld+ndDN7sjgt0bIVLBITdR2K1CcVyPMDCZ2qZB0yiuDbXDQOZJkdrq89
55BUKrK7h5KLI5Ad8z5cGsyeK5nY3TUXmuPsdl0Pk/Lbu5m+EfxxxuQw0EljBhY9
UOasXcQ8VAXut0k4banTNFrY07TCM3gHMN2qRKTGiabtq/gh17ez/DejTVt3+2Ru
1Qi9XUVpL1mLwWsrqhI4JIe/zhpJS4eJizvP4Dywp+0pdplSPJVV9tybFWiojdfP
zt/4IQD0YHosTdxIEPyLWZBuszyG0TDmsQYyt29cXYzQeZSge+T1CF9TfEcX1wY=
=tSMU
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-05-31 17:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-27 19:10 Jeff Law
2011-05-30 12:34 ` Bernd Schmidt
2011-05-31 18:33 ` Jeff Law [this message]
2011-06-14 15:38 Jeff Law
2011-06-22 15:33 ` Bernd Schmidt
2011-06-23 21:34 ` Jeff Law
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=4DE529A5.2070902@redhat.com \
--to=law@redhat.com \
--cc=bernds@codesourcery.com \
--cc=gcc-patches@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).