This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [patch] jump threading multiple paths that start from the same BB




On 07/09/2018 04:29 AM, Richard Biener wrote:
On Mon, Jul 9, 2018 at 9:19 AM Aldy Hernandez <aldyh@redhat.com> wrote:



On 07/05/2018 03:27 PM, Jeff Law wrote:
On 07/04/2018 02:12 AM, Aldy Hernandez wrote:

Many tests should turn into gimple IL tests.

Yeah, though for tests like the threading ones, they're already
sufficiently convoluted that turning them into gimple IL tests will make
them even harder to read.  Oh well, I guess?

To make it easier to transition to gimple IL tests, I suppose we could
add -fdump-tree-*-something-more-suitable-for-gimplefe ;-).

There is -fdump-tree-*-gimple ;)

Ahh!!!  Thanks.


Is it by
design that the gimple fe is sufficiently different from what we dump
for -fdump-tree (ahem, things like phi arguments, probabilities, etc)?

Well.  The only reason is that I didnt' want to adjust all testcases so
I introduced the -gimple dump modifier...

Note there's still some "magic" fiddling needed to make the GIMPLE FE
grok -gimple dump files as well as working around limitations with the
current way of having SSA/CFG testcases.

I'll keep it in mind as I deal with threading going forward.



And I'd like a better framework for testing what we're doing to the IL.

Sigh.  Me too.

Well, the GIMPLE FE is supposed to be that - it's just not perfect
(or rather incomplete).

Hey, it's pretty good IMO :).

Thanks.
Aldy


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]