This is the mail archive of the
mailing list for the GCC project.
Re: [PATCH RFC]Pair load store instructions using a generic scheduling fusion pass
- From: Mike Stump <mikestump at comcast dot net>
- To: Richard Biener <richard dot guenther at gmail dot com>
- Cc: "Bin.Cheng" <amker dot cheng at gmail dot com>, Bin Cheng <bin dot cheng at arm dot com>, gcc-patches List <gcc-patches at gcc dot gnu dot org>, Jeff Law <law at redhat dot com>
- Date: Mon, 6 Oct 2014 10:20:03 -0700
- Subject: Re: [PATCH RFC]Pair load store instructions using a generic scheduling fusion pass
- Authentication-results: sourceware.org; auth=none
- References: <000001cfdc90$1d95c670$58c15350$ at arm dot com> <781A4573-F7ED-4ABD-B222-76F2044E641A at comcast dot net> <CAHFci29=8H_qQSCwUUMWgdyX-DQziE8hSagM7CDNBEMkrXo+3w at mail dot gmail dot com> <CAFiYyc14oz1x309XF08hZHN1UbfuP9PxMQH0x5V5GBDePN4Cvw at mail dot gmail dot com>
On Oct 6, 2014, at 4:32 AM, Richard Biener <firstname.lastname@example.org> wrote:
> On Mon, Oct 6, 2014 at 11:57 AM, Bin.Cheng <email@example.com> wrote:
> How many merging opportunities does sched2 undo again? ISTR it
> has the tendency of pushing stores down and loads up.
So, the pass works by merging 2 or more loads into 1 load (at least on my port). sched2 would need to rip apart 1 load into 2 loads to be able to undo the real work. The non-real work, doesn’t matter any. Can sched2 rip apart a single load?