Re:New optimizations for X86 in upcoming GCC 5.0: PIC in 32 ...
by makomk on Wednesday April 15, 2015 @07:16AM
(#9380133)
Presumably they've fixed it so that the GOT only has to be in a register whilst code is actually using it, and can be spilled to the stack at other times. Tight loops probably aren't going to be accessing the GOT in the inner loop - ideally they'll obtain a pointer to any global data they use at the start and use that, so it makes sense to move the GOT pointer elsewhere for the duration of the loop.
[ Parent
| on HN ]
There are no comments on this comment yet.