diff options
| author | Xi Ruoyao <xry111@xry111.site> | 2022-09-20 14:09:29 +0800 |
|---|---|---|
| committer | liuzhensong <liuzhensong@loongson.cn> | 2022-09-20 17:16:05 +0800 |
| commit | 6224a6c2ead26a04f0b2b8ccf4ff5b817afbb425 (patch) | |
| tree | 02df20b432fad41fa61a7cc3c7a58b2378d2ec43 /config-ml.in | |
| parent | 6519cd1a15fda2b67ae3e4ad8a2758615d3e0f9f (diff) | |
| download | binutils-6224a6c2ead26a04f0b2b8ccf4ff5b817afbb425.zip binutils-6224a6c2ead26a04f0b2b8ccf4ff5b817afbb425.tar.gz binutils-6224a6c2ead26a04f0b2b8ccf4ff5b817afbb425.tar.bz2 | |
LoongArch: Don't write into GOT for local ifunc
Local ifuncs are always resolved at runtime via R_LARCH_IRELATIVE, so
there is no need to write anything into GOT. And when we write the GOT
we actually trigger a heap-buffer-overflow: If a and b are different
sections, we cannot access something in b with "a->contents + (offset
from a)" because "a->contents" and "b->contents" are heap buffers
allocated separately, not slices of a large buffer.
So stop writing into GOT for local ifunc now.
Diffstat (limited to 'config-ml.in')
0 files changed, 0 insertions, 0 deletions