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
