Liste des Groupes | Revenir à cl c |
On Mon, 25 Nov 2024 13:45:28 +0100That is quite plausible. I only occasionally have use for objdump, and I suspect many programmers never use it at all. I doubt if I'd use the lto-dump version much if and when I start using LTO seriously.
David Brown <david.brown@hesbynett.no> wrote:>I am pretty sure that even if I ever want to use LTO with gcc I'd still
LTO object files are vastly different beasts from normal object
files, so it does not surprise me that the dump utility is so much
bigger. If you don't use LTO, then presumably you will not need the
lto-dump utility. (It is not a tool I have ever looked at myself.)
>
will have no need for lto-dump.
What would matter for me in this caseAgain, I don't doubt you are correct.
would be a final result (exe) rather than object files. And in order to
look at exe I'd still use a normal objdump.
The situation is not purely hypothetical. I regularly use LTCG with
Microsoft tools. Never ever I wanted to disassemble .obj files after
LTCG compilation. When occasionally I wanted to look at asm after LTCG,
it always was an exe.
Les messages affichés proviennent d'usenet.