public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <law@redhat.com>
To: Andi Kleen <andi@firstfloor.org>, gcc-patches@gcc.gnu.org
Cc: Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH] Always print attributes when dumping tree
Date: Fri, 23 Jun 2017 04:46:00 -0000	[thread overview]
Message-ID: <ed188af5-637e-d596-9486-631eb3baa577@redhat.com> (raw)
In-Reply-To: <20170517021835.8685-1-andi@firstfloor.org>

On 05/16/2017 08:18 PM, Andi Kleen wrote:
> From: Andi Kleen <ak@linux.intel.com>
> 
> A tree type dump currently doesn't print the attributes. Since we have
> so many now and they do many interesting things dumping them can be
> useful. So dump them by default for tree type dumps.
> 
> Passes bootstrap and testing on x86_64-linux.
> 
> gcc/:
> 
> 2017-05-16  Andi Kleen  <ak@linux.intel.com>
> 
>         * print-tree.c (print_node): Print all attributes.
OK for the trunk.

Thanks,
Jeff

      reply	other threads:[~2017-06-23  4:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-17  2:45 Andi Kleen
2017-06-23  4:46 ` Jeff Law [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=ed188af5-637e-d596-9486-631eb3baa577@redhat.com \
    --to=law@redhat.com \
    --cc=ak@linux.intel.com \
    --cc=andi@firstfloor.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).