This is the mail archive of the
mailing list for the GCC project.
Re: [RFC]: Remove Mem/address type assumption in combiner
- From: Jeff Law <law at redhat dot com>
- To: Segher Boessenkool <segher at kernel dot crashing dot org>, "Kumar, Venkataramanan" <Venkataramanan dot Kumar at amd dot com>
- Cc: "gcc-patches at gcc dot gnu dot org" <gcc-patches at gcc dot gnu dot org>, "maxim dot kuvyrkov at linaro dot org" <maxim dot kuvyrkov at linaro dot org>
- Date: Wed, 29 Apr 2015 13:10:57 -0600
- Subject: Re: [RFC]: Remove Mem/address type assumption in combiner
- Authentication-results: sourceware.org; auth=none
- References: <7794A52CE4D579448B959EED7DD0A4723DCE9F34 at satlexdag06 dot amd dot com> <20150429170335 dot GB21715 at gate dot crashing dot org>
On 04/29/2015 11:03 AM, Segher Boessenkool wrote:
Right. ANd that was one of the two general directions I recommended
earlier this week ;-)
Right. It would be good if you could find out for what targets it matters.
The thing is, if a target expects only the patterns as combine used to make
them, it will regress (as you've seen on aarch64); but it will regress
_silently_. Which isn't so nice.
But before that I wanted to check if the assumption in combiner, can simply be removed ?
Seeing for what targets / patterns it makes a difference would tell us the
answer to that, too :-)
1. Figure out if this code still matters at all.
2. If the code still matters, accurately track if we're
inside a MEM so that things canonicalize correctly.