public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Paul Richard Thomas <paul.richard.thomas@gmail.com>
To: Thomas Koenig <tkoenig@netcologne.de>
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 13:15:00 -0000	[thread overview]
Message-ID: <CAGkQGi+S6Z8FMpK4sSkRN7=6FPrYP+hWWrhuKiMZ63r-Sj-sQw@mail.gmail.com> (raw)
In-Reply-To: <44982d74-aac3-c2dd-7395-146362af16f3@netcologne.de>

Hi Thomas,

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.

Thanks for working on -fdump-parse-tree.

Cheers

Paul

On 8 October 2017 at 13:57, Thomas Koenig <tkoenig@netcologne.de> wrote:
> Hello world,
>
> I have committed a few small fixes for -fdump-fortran-original and
> friends.
>
> Since there was interest on c.l.f from somebdoy who actually wanted to
> use the dump for something useful, I have also clarified in the docs
> that this is something that is not guaranteed to work between releases.
>
> Regards
>
>         Thomas
>
> 2017-10-08  Thomas Koenig  <tkoenig@gcc.gnu.org>
>
>         * dump_prase_tree (show_symbol): Output list of variables in
>         NAMELIST.
>         (show_code_node): Add new line for ELSE and END DO for DO
>         CONCURRENT.
>         * invoke.texi: Document that the output of
>         -fdump-fortran-original, -fdump-fortran-optimized and
>         -fdump-parse-tree is unsable and may lead to ICEs.



-- 
"If you can't explain it simply, you don't understand it well enough"
- Albert Einstein

  reply	other threads:[~2017-10-08 13:15 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 [this message]
2017-10-08 14:18   ` Thomas Koenig
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='CAGkQGi+S6Z8FMpK4sSkRN7=6FPrYP+hWWrhuKiMZ63r-Sj-sQw@mail.gmail.com' \
    --to=paul.richard.thomas@gmail.com \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=tkoenig@netcologne.de \
    /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).