From: Andi Kleen <andi@firstfloor.org>
To: gcc-patches@gcc.gnu.org
Cc: Andi Kleen <ak@linux.intel.com>
Subject: [PATCH] Always print attributes when dumping tree
Date: Wed, 17 May 2017 02:45:00 -0000 [thread overview]
Message-ID: <20170517021835.8685-1-andi@firstfloor.org> (raw)
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.
---
gcc/print-tree.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gcc/print-tree.c b/gcc/print-tree.c
index e0db2dfe82e..f9af02f4e42 100644
--- a/gcc/print-tree.c
+++ b/gcc/print-tree.c
@@ -485,7 +485,7 @@ print_node (FILE *file, const char *prefix, tree node, int indent,
if (CODE_CONTAINS_STRUCT (code, TS_DECL_COMMON))
{
- print_node_brief (file, "attributes",
+ print_node (file, "attributes",
DECL_ATTRIBUTES (node), indent + 4);
if (code != PARM_DECL)
print_node_brief (file, "initial", DECL_INITIAL (node),
--
2.12.2
next reply other threads:[~2017-05-17 2:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-17 2:45 Andi Kleen [this message]
2017-06-23 4:46 ` 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=20170517021835.8685-1-andi@firstfloor.org \
--to=andi@firstfloor.org \
--cc=ak@linux.intel.com \
--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).