This is the mail archive of the binutils@sources.redhat.com mailing list for the binutils project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
I think that if readelf has to guess it should inform the user that it is doing so. That way the user has a chance to realise that readelf might have guessed incorrectly and that is why its output does not match their expectations.
Any chance of persuading you otherwise? ;)
- It doesn't seem very useful to print a warning if the user has no
way of overriding the guess.
If we do warn about this, I suppose we'd also have to add a MIPS-EABI64-specific command-line option to readelf, and like I said in my original posting, I'd really rather not do that. There's certainly no precedent with the existing options.
- I don't want to warn about unmarked LP64 objects since there's nothing suspect about them. They do exactly what the official ABI said they should do.
- People only ended up with unmarked ILP32 objects through using an
undocumented combination of gcc command-line options. I think it's reasonable for tools like readelf (and gdb, etc.) to treat
EABI objects as being ABI-conforming without any evidence to
the contrary.
Cheers Nick
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |