Rui Ueyama

Ah, `__start`/`__stop` symbols are by default global in BFD. Here is a quote from GNU ld's man page. ``` start-stop-visibility=value Specify the ELF symbol visibility for synthesized "__start_SECNAME" and "__stop_SECNAME"...

We may want to ignore `-z start-stop-visibility=hidden` for the sake of compatibility with programs that follow the recommendation in this man page. Other than that, I don't think there's a...

I don't want to change the mold's default from `-z start-stop-visibility=hidden` to `-z start-stop-visibility=protected`, but I'm open to support `-z start-stop-visibility=protected`.

Actually I've already started working on it.

It's hard to debug it without reproducing it locally. If it's open source, please let me know the location of your repo. If not, you can share me object files...

Can you re-link your kernel with `--repro` and upload a generated `kernel.elf.tar`? That tar file will contain all input files so that I can build it on my local machine...

I ran `mold` with your input files and it just passed. It indeed called ftruncate(2) but with a reasonable argument as follows (this is an strace log): ``` ftruncate(3, 284136)...

Are you building your kernel on a 32-bit machine?

I can add the `--hash-style=none` option for use cases like yours to negate previous `--hash-style` options, so that you can eliminate `.gnu.hash` or `.hash` from your library. We can't simply...

Just truncating an ELF file to remove trailing null bytes doesn't seem like a safe optimisation. It's generally not supposed to work.