Martin Liška

Yeah, I noticed your recent commits that were prefixed as `PPC64`. It may be better to prefix them with `PPC64LE` ;) Are you interested in test-result on `ppc64le` system I...

Great, so for cda57cfe4a8107dc4d188b8057a72a31cafef6d4 I see: ``` ... Testing filler ... mold: fatal: /usr/lib64/libc.a(errno.o):(.debug_info): apply_reloc_nonalloc: R_PPC64_DTPREL64 collect2: error: ld returned 1 exit status make[1]: *** [Makefile:211: test/elf/filler.sh] Error 1 ......

> I think I can fix the first issue easily. The second valgrind issue is a bit mysterious. Can you share that executable valgrind is complaining with me? Sure: [section-start.tar.gz](https://github.com/rui314/mold/files/9546244/section-start.tar.gz)...

> Maybe I need an access to a real machine. You should definitely create an account for GCC Compiler Farm: https://gcc.gnu.org/wiki/CompileFarm https://cfarm.tetaneutral.net/users/new/ Where we have a rich variety of machines:...

> By the way, do you think mold's multi-target support is good enough? From `SUSE` and `openSUSE` perspectives it's good. Right now, we do support `x86_64`, `aarch64`, 'ppc64le' and `s390x`...

> Is s390x PPC64LE or something else? No, It's IBM mainframe architecture: https://en.wikipedia.org/wiki/IBM_Z

> Your binary works fine on qemu-ppc64le, so I'm not sure what's wrong. Same for me!

So the remaining issue is somehow caused by debug info, because: ``` $ strip out/test/elf/ppc64le/section-start/exe $ out/test/elf/ppc64le/section-start/exe Hello world ```

and `objdump -D` complains: ``` objdump -D out/test/elf/ppc64le/section-start/exe 2>&1 | grep -U5 'is out' 2003ec: 47 4c 49 42 bcla 18,4*cr2+gt,4c44 2003f0: 43 5f 32 2e cmpdi cr4,r18,24387 2003f4: 31...

It works! The wild one was the correct one.