Remove remaining R_X86_64_GOTOFF64

Remove R_X86_64_GOTOFF64 as grimar@ suggested

Rename test file as grimar@ suggested

Friendly ping :)

I hadn't noticed the better proposal when I sent this one out. I'll abandon this revision

.

don't change QualifiedName

Catch StdQualifiedName and AbiTagAttr

test

CHECK-NEXT:

format

Add case R_X86_64_GOTPC64: (used in -mcmodel=large)

Update tests

update

Sorry for being unclear. I mean that code also wants to avoid a division instruction. Is that because the symbols are iterated NumSymbols*Concurrency times to the saving is significant but other alignment improvement may be unnoticeable?

I found this when I was reading how SHF_MERGE sections are merged. Why does the code claim that power of 2 makes the parallelism more efficient?

They may be applicable in some places of LLD, e.g.

Is the bot able to give more diagnostics information?

Delete checkBackrefs.

This is not a bug in glibc if we don't take behavior difference as a bug. bfd/gold seem to add a CIE of length=0 anyway so this piece of glibc/libgcc_s libunwind code won't go wrong.

last_fde is defined at https://code.woboq.org/userspace/glibc/sysdeps/generic/unwind-dw2-fde.h.html#162 . It does not check whether it reaches the end of .eh_frame (DWARF2_OBJECT_END_PTR_EXTENSION seems not defined). If there is no length=0 terminator, the pointer will run beyond the end of .eh_frame and run into successive sections (out-of-bound read), segfault or stop somewhere. This issue is usually latent/benign and I can only catch this in some internal statically-linked configuration. I don't have time to read the whole source code of how glibc/libgcc_s libunwind to understand why this routine is sometimes called but sometimes not.

A real world example:

Add -o %t.exe

The root cause is that IFUNC (e.g. R_X86_64_IRELATIVE) is incompatible with DF_TEXTREL.

Update test

Can this script be made Python 3 compatible? Here is one place where running it under python3 will fail

Hi Raphael, sorry for hearing that... But may I beg your last review at this revision, considering it was created before your announcement?

The test does not change.