aboutsummaryrefslogtreecommitdiff
path: root/binutils/ChangeLog
diff options
context:
space:
mode:
authorAlan Modra <amodra@gmail.com>2015-02-26 21:26:42 +1030
committerAlan Modra <amodra@gmail.com>2015-02-26 21:49:54 +1030
commitbd4d2eaad0f624bc47b2e27222480a44d1a48108 (patch)
tree32e794259808ecc381c0bc30ae2ecf5485d3d43d /binutils/ChangeLog
parentcf424aef0af89903abdd6c4e055684929e4990af (diff)
downloadgdb-bd4d2eaad0f624bc47b2e27222480a44d1a48108.zip
gdb-bd4d2eaad0f624bc47b2e27222480a44d1a48108.tar.gz
gdb-bd4d2eaad0f624bc47b2e27222480a44d1a48108.tar.bz2
PowerPC64 thread-safe stubs not needed for iplt
I was looking at a current glibc using objdump today and saw an odd plt call stub. 0000000000044d80 <00000033.plt_call.__strchrnul>: 44d80: f8 41 00 28 std r2,40(r1) 44d84: e9 82 8c f8 ld r12,-29448(r2) 44d88: 7d 89 03 a6 mtctr r12 44d8c: e8 42 8d 00 ld r2,-29440(r2) 44d90: 28 22 00 00 cmpldi r2,0 44d94: 4c e2 04 20 bnectr+ 44d98: 48 13 84 f0 b 17d288 <realloc@plt> What? It doesn't branch to __strchrnul@plt on finding a zero r2? Turns out this isn't a real problem since the stub is for loading an ifunc, so will not be lazily resolved and thus r2 will never be zero. Of course, that means the thread-safety check is unnecessary. I also tweak the special __tls_get_addr_opt call stub here, to restore r2 immediately after the call. Not doing that might affect eh_frame unwinding. * elf64-ppc.c (plt_stub_size, build_plt_stub): Don't build thread-safe stubs for iplt. (build_tls_get_addr_stub): Restore r2 immediately after call.
Diffstat (limited to 'binutils/ChangeLog')
0 files changed, 0 insertions, 0 deletions