From: Michael Matz <matz@suse.de>
To: David Malcolm <dmalcolm@redhat.com>
Cc: Martin Sebor <msebor@gmail.com>,
Segher Boessenkool <segher@kernel.crashing.org>,
gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] final: Improve output for -dp and -fverbose-asm
Date: Mon, 04 Dec 2017 15:49:00 -0000 [thread overview]
Message-ID: <alpine.LSU.2.21.1712041632560.25295@wotan.suse.de> (raw)
In-Reply-To: <1512063985.27881.50.camel@redhat.com>
Hi,
On Thu, 30 Nov 2017, David Malcolm wrote:
> -fverbose-asm is on the border of compiler-debugging vs end-user usage.
I have yet to see a relevant percentage of end-users who even know what
assembler is. On the gcc.*@ and kernel.* mailing lists, sure. But Joe
Randomapp?
> FWIW an improvement to -fverbose-asm was explicitly mentioned in the
> gcc 7 release notes:
> https://gcc.gnu.org/gcc-7/changes.html
> and I've seen at least some end-users comment favorably on that change;
> this was:
> https://gcc.gnu.org/ml/gcc-patches/2016-08/msg01051.html
> which was originally a "-fasm-show-source" option.
Yes. I think this was actually a disservice to readability of
-fverbose-asm (sorry!) and would have preferred a suboption as well (but
wouldn't have complained if with-sources would be the default). First, it
clutters the asm instructions with intervening non-aligned lines (and
left-hanging even, giving more visual importance to them instead of what
is actually important, which for a switch named verbose-asm seems the asm
to me) and second it has the same problem as debugging scheduled code:
jumping around crazy and stating the same source line multiple times.
(Basically the same reason 'objdump -dS' is similarly ugly, and why the -S
therein is an extra switch).
Luckily -dp still works as expected, so, ... well, I guess I'll live, and
if not there's "grep -v '^#.*:[0-9]\+:'" :)
Ciao,
Michael.
next prev parent reply other threads:[~2017-12-04 15:49 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-29 23:37 Segher Boessenkool
2017-11-30 7:52 ` Martin Sebor
2017-11-30 11:54 ` Segher Boessenkool
2017-11-30 16:06 ` Michael Matz
2017-11-30 16:36 ` Martin Sebor
2017-11-30 16:50 ` Segher Boessenkool
2017-11-30 17:02 ` Martin Sebor
2017-11-30 17:14 ` Michael Matz
2017-11-30 17:55 ` Martin Sebor
2017-12-01 0:32 ` Jeff Law
2017-12-01 22:52 ` Segher Boessenkool
2017-12-04 12:39 ` Michael Matz
2017-11-30 17:55 ` David Malcolm
2017-12-04 15:49 ` Michael Matz [this message]
2017-11-30 17:15 ` Segher Boessenkool
2017-11-30 22:59 ` Martin Sebor
2017-12-01 0:26 ` Jeff Law
2017-12-01 0:49 ` Jeff Law
2017-12-01 23:45 ` Segher Boessenkool
2017-11-30 16:44 ` Kyrill Tkachov
2017-11-30 16:54 ` Michael Matz
2017-11-30 16:55 ` Kyrill Tkachov
2017-11-30 17:07 ` Michael Matz
2017-12-01 0:22 ` Jeff Law
2017-12-01 0:25 ` Jeff Law
2017-12-01 1:17 ` Jeff Law
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=alpine.LSU.2.21.1712041632560.25295@wotan.suse.de \
--to=matz@suse.de \
--cc=dmalcolm@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=msebor@gmail.com \
--cc=segher@kernel.crashing.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: link
Be 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).