From: Jeff Law <law@redhat.com>
To: Segher Boessenkool <segher@kernel.crashing.org>,
"Kumar, Venkataramanan" <Venkataramanan.Kumar@amd.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
"maxim.kuvyrkov@linaro.org" <maxim.kuvyrkov@linaro.org>
Subject: Re: [RFC]: Remove Mem/address type assumption in combiner
Date: Wed, 29 Apr 2015 19:23:00 -0000 [thread overview]
Message-ID: <55412CC1.1070401@redhat.com> (raw)
In-Reply-To: <20150429170335.GB21715@gate.crashing.org>
On 04/29/2015 11:03 AM, Segher Boessenkool wrote:
>
> 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 :-)
Right. ANd that was one of the two general directions I recommended
earlier this week ;-)
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.
jeff
next prev parent reply other threads:[~2015-04-29 19:11 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-29 9:29 Kumar, Venkataramanan
2015-04-29 17:38 ` Segher Boessenkool
2015-04-29 19:23 ` Jeff Law [this message]
2015-05-01 15:18 ` Segher Boessenkool
2015-05-05 16:14 ` Kumar, Venkataramanan
2015-05-05 17:15 ` Segher Boessenkool
2015-05-07 11:01 ` Kumar, Venkataramanan
2015-05-11 17:50 ` Steve Ellcey
2015-05-11 18:27 ` Segher Boessenkool
2015-05-11 19:44 ` Steve Ellcey
2015-05-11 19:46 ` Jeff Law
2015-05-11 19:46 ` Jeff Law
2015-05-11 20:17 ` Matthew Fortune
2015-05-11 20:30 ` Segher Boessenkool
2015-05-11 20:54 ` Matthew Fortune
2015-05-12 6:43 ` Kumar, Venkataramanan
2015-05-12 16:57 ` Steve Ellcey
2015-05-12 22:02 ` Moore, Catherine
2015-05-16 6:09 ` Hans-Peter Nilsson
2015-05-16 14:36 ` Segher Boessenkool
2015-05-16 16:43 ` Hans-Peter Nilsson
2015-05-16 17:40 ` Segher Boessenkool
2015-05-17 8:53 ` Hans-Peter Nilsson
2015-05-17 13:32 ` Segher Boessenkool
2015-05-17 13:48 ` Hans-Peter Nilsson
2015-05-19 17:30 ` Jeff Law
2015-04-29 19:22 ` Jeff Law
2015-04-29 19:31 ` 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=55412CC1.1070401@redhat.com \
--to=law@redhat.com \
--cc=Venkataramanan.Kumar@amd.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=maxim.kuvyrkov@linaro.org \
--cc=segher@kernel.crashing.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).