https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92308
--- Comment #5 from rguenther at suse dot de <rguenther at suse dot de> --- On Mon, 4 Nov 2019, rearnsha at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92308 > > --- Comment #4 from Richard Earnshaw <rearnsha at gcc dot gnu.org> --- ... > But there's no real need to do this by splitting the bits with a mask, if we > have a global view of what's going on (the problem is that > TARGET_LEGITIMIZE_ADDRESS does not have a global view); we could pick the > original BB_ADDRESS as the base just as easily as any other. Note no GIMPLE pass has "a global view" on uses of constants either, that would need to be invented. IMHO this is close enough to constant pool optimizations that doing this on GIMPLE where there's no concept of a constant pool entry vs an immediate sounds wrong until we introduce that idea there. I suspect TARGET_LEGITIMIZE_ADDRESS is only applied during reload/LRA, correct?
