public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug driver/66657] Feature request - assembly output from lto compiler Date: Wed, 01 Sep 2021 22:24:13 +0000 [thread overview] Message-ID: <bug-66657-4-O9KthrvyrQ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-66657-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66657 --- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> --- (In reply to Kenneth Almquist from comment #3) > (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. For recent compilers you can use -fopt-info option which should supply this; if it does not then we should improve it to supply what you need. > > 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. For this, as mentioned you can use post tools like objdump/nm/etc. and even the you can use a GNU linker option to warn at link time.
prev parent reply other threads:[~2021-09-01 22:24 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-06-24 20:35 [Bug driver/66657] New: " kalmquist1 at hotmail dot com 2015-06-24 20:36 ` [Bug driver/66657] " pinskia at gcc dot gnu.org 2015-06-25 21:51 ` kalmquist1 at hotmail dot com 2021-09-01 22:24 ` pinskia at gcc dot gnu.org [this message]
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-66657-4-O9KthrvyrQ@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).