Re: Best reference for understanding ELF format

[Peng Yu <pengyu.ut@gmail.com>]

On 4/20/21, Mike Frysinger <vapier@gentoo.org> wrote:
> On 19 Apr 2021 20:58, Peng Yu via Libc-help wrote:
>> On 4/19/21, Szabolcs Nagy <szabolcs.nagy@arm.com> wrote:
>> > The 04/17/2021 07:31, Peng Yu via Libc-help wrote:
>> >> That is a book. By definition, a book will not be complete since a
>> >> book is not written for completeness?
>> >>
>> >> For the best reference (as "reference" may have muliple meanings maybe
>> >> I should use the word "spec" to avoid ambiguity), I found the
>> >> following two documents. One is for 32-bit, the other is for 64-bit.
>> >> Are they the most current ones? Other there any other documents that
>> >> cover the things missed by them?
>> >>
>> >> https://refspecs.linuxfoundation.org/elf/elf.pdf
>> >> https://www.uclibc.org/docs/elf-64-gen.pdf
>> >
>> > elf spec is part of the system v abi document.
>> > the generic part is in
>> > http://www.sco.com/developers/gabi/
>> > the processor specific part is published separately by
>> > whoever does the tooling for the particular processor.
>> >
>> > (all this can be found out by 5 minute research on wikipedia)
>> >
>> > but since you asked for easy-to-follow and for
>> > understanding elf i think the book is better.
>>
>> Updated is also needed. An outdated reference is not preferred even it
>> is easy to follow.
>
> pretty much all the content in the book is still relevant.  the fact that
> it
> doesn't cover the latest ELF extensions doesn't mean that the fundamentals
> are
> no longer relevant.
>
>> I found this book is quite outdated. It does not explain the current
>> gcc and clang.
>
> gcc & clang don't produce ELFs.

Then what produces ELFs? gcc/clang output files in ELFs. I don't
understand what you mean here.

>  so, at best, they'd be mentioned in
> passing
> even in the latest docs.
>
>> For example, gcc mostly use RELA instead of REL. But this book says this.
>
> gcc doesn't generate relocations.

Again. gcc produces files with relocations. Do you mean gcc does not
produce them directly (instead gcc some other tools to produce an ELF
file with relocations)?

> also "mostly" is a bit skewed.  it depends on the architecture.
>
>> So a better reference in terms of all three aspects that I mentioned is
>> needed.
>
> you need to learn to walk before you can hope to run.

Please provide useful information instead of nonsense like this.

-- 
Regards,
Peng