This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug driver/66657] Feature request - assembly output from lto compiler
- From: "kalmquist1 at hotmail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Thu, 25 Jun 2015 21:51:31 +0000
- Subject: [Bug driver/66657] Feature request - assembly output from lto compiler
- Auto-submitted: auto-generated
- References: <bug-66657-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66657
--- Comment #3 from Kenneth Almquist <kalmquist1 at hotmail dot com> ---
(In reply to Andrew Pinski from comment #2)
> What are you trying to do with the assembly after the fact?
In this particular case, I wanted to look at it for two reasons:
1) To determine which functions were being inlined.
2) To identify errant calls to printf and puts. When compiled to run in
background mode, my program should send all messages to the log rather than
stdout/stderr, so calls to printf/puts that the compiler doesn't discard as
unreachable represent program bugs.
Gcc has had the -S option for essentially forever, and I've probably used it
more times and for more reasons than I can remember at this point.