diff options
| author | H. Peter Anvin <hpa@zytor.com> | 2008-10-17 22:11:20 -0700 |
|---|---|---|
| committer | H. Peter Anvin <hpa@zytor.com> | 2008-10-17 22:11:20 -0700 |
| commit | bdfd3b3b87b6f9e912724bff1cf3f6aa34cc9efe (patch) | |
| tree | 11dcf06da6ad47d22199fa030b1c3f6dd6986d93 | |
| parent | 15ed76867307abca4f732a0eb536f2fad2914767 (diff) | |
| download | nasm-bdfd3b3b87b6f9e912724bff1cf3f6aa34cc9efe.tar.gz | |
ELF64: We apparently don't need exactitude for GOTOFF64
I am having a bit of a hard time understanding the proper operation of
the "exact" flag to elf_add_gsym_reloc(). We apparently won't
generate proper GOTOFF64 relocations with this flag set; it is
possible that there are *no* proper uses of this flag. This clearly
needs to be figured out.
Signed-off-by: H. Peter Anvin <hpa@zytor.com>
| -rw-r--r-- | output/outelf64.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/output/outelf64.c b/output/outelf64.c index 3e9f7767..1405d2fd 100644 --- a/output/outelf64.c +++ b/output/outelf64.c @@ -1013,7 +1013,7 @@ static void elf_out(int32_t segto, const void *data, "references to be qword absolute"); } else { elf_add_gsym_reloc(s, segment, addr, 0, - R_X86_64_GOTOFF64, true); + R_X86_64_GOTOFF64, false); addr = 0; } } else if (wrt == elf_got_sect + 1) { |