From: Thomas Koenig <tkoenig@netcologne.de>
To: "fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: *ping* [patch, fortran] Two associate fixes in dump-parse-tree.c
Date: Sun, 28 Feb 2016 11:42:00 -0000 [thread overview]
Message-ID: <56D2DD2A.2040605@netcologne.de> (raw)
In-Reply-To: <56C0D530.9060406@netcologne.de>
I wrote:
Patch at
https://gcc.gnu.org/ml/gcc-patches/2016-02/msg00941.html
> OK for trunk?
>
> Regards
>
> Thomas
>
> 2016-02-14 Thomas Koenig <tkoenig@gcc.gnu.org>
>
> * dump-parse-tree.c (show_code_node): Print association
> list of a block if present. Handle EXEC_END_BLOCK.
next prev parent reply other threads:[~2016-02-28 11:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-14 19:27 Thomas Koenig
2016-02-28 11:42 ` Thomas Koenig [this message]
2016-02-28 18:40 ` *ping* " Jerry DeLisle
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=56D2DD2A.2040605@netcologne.de \
--to=tkoenig@netcologne.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@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: 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).