From: Thomas Koenig <tkoenig@netcologne.de>
To: Paul Richard Thomas <paul.richard.thomas@gmail.com>
Cc: "fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [patch, fortran, committed] Small -fdump-fortran-original fixes, plus documentation update
Date: Sun, 08 Oct 2017 14:18:00 -0000 [thread overview]
Message-ID: <a68ba0f8-d326-8dcc-d673-f34383a69792@netcologne.de> (raw)
In-Reply-To: <CAGkQGi+S6Z8FMpK4sSkRN7=6FPrYP+hWWrhuKiMZ63r-Sj-sQw@mail.gmail.com>
Hi Paul,
> I thought that the suggestion to add the original input lines was not
> bad. It would be even better if -fdump-tree-original could do that. I
> often time find myself putting a line under the spotlight in a
> contained subroutine.
This should be doable.
What should be the perferred format?
Something like
filename:line\tOutput goes here
would be possible, or without the file name
line\tOutput goes here
The latter would have the advantage that it would be fairly easy to
line up the declarations from modules, which probably should not
have line number annotations.
And what would be preferred - having a new option to control line
numbering, or doing it unconditionally?
Regards
Thomas
next prev parent reply other threads:[~2017-10-08 14:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-08 12:57 Thomas Koenig
2017-10-08 13:15 ` Paul Richard Thomas
2017-10-08 14:18 ` Thomas Koenig [this message]
2017-10-08 14:46 ` Mikael Morin
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=a68ba0f8-d326-8dcc-d673-f34383a69792@netcologne.de \
--to=tkoenig@netcologne.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=paul.richard.thomas@gmail.com \
/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).