------- Comment #29 from kkojima at gcc dot gnu dot org 2010-02-03 10:06 ------- I think these blockages are not overkill. GOTaddr2picreg is used only at prologue and non-pic tls initial exec accesses. The former is at most once for each function and never in the minor loop. The latter case wouldn't occur so frequently and the initial exec access is loaded sequence of instructions in the first place.
> We only want to avoid the CP to be inserted between those 2 instructions, > it's not necessary to have more blockages. I'm working on something that > tracks the GOT loading access during the find_barrier walk and then revert > back at the end to the latest safe place. OK on the example but the full > linux distrib rebuild and validation is still ongoing. Of course, it's OK if it passes all the usual tests. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42841
