This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [RFC 4/5] Handle constant-pool entries
- From: Alan Lawrence <alan dot lawrence at arm dot com>
- To: Jeff Law <law at redhat dot com>
- Cc: "gcc-patches at gcc dot gnu dot org" <gcc-patches at gcc dot gnu dot org>, "rguenther at suse dot de" <rguenther at suse dot de>, "mjambor at suse dot cz" <mjambor at suse dot cz>
- Date: Wed, 26 Aug 2015 16:37:23 +0100
- Subject: Re: [RFC 4/5] Handle constant-pool entries
- Authentication-results: sourceware.org; auth=none
- References: <1440500777-25966-1-git-send-email-alan dot lawrence at arm dot com> <1440500777-25966-5-git-send-email-alan dot lawrence at arm dot com> <55DCCC65 dot 4050000 at redhat dot com>
Jeff Law wrote:
The question I have is why this differs from the effects of patch #5.
That would seem to indicate that there's things we're not getting into
the candidate tables with this approach?!?
I'll answer this first, as I think (Richard and) Martin have identified enough
other issues with this patch that will take longer to address.... but if you
look at the context to the hunk in patch 5, it is iterating through the
candidates (from patch 4), and then filtering out any candidates bigger than
max-scalarization-size, which filtering patch 5 removes.
--Alan