public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "steven at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/54150] [4.8 Regression] gimple dumps no longer honor -blocks
Date: Wed, 01 Aug 2012 13:18:00 -0000 [thread overview]
Message-ID: <bug-54150-4-UNltbNuxEd@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54150-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54150
Steven Bosscher <steven at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2012-08-01
Ever Confirmed|0 |1
--- Comment #2 from Steven Bosscher <steven at gcc dot gnu.org> 2012-08-01 13:18:06 UTC ---
(In reply to comment #0)
> That said, the tree dumps still look remarkably ugly by default now.
That is a debate of taste that I don't think we ought to get into.
I had technical reasons why I made this so: Various scripts that do CFG
analysis can now parse GIMPLE and RTL dumps without modification.
The dumper should honor TDF_BLOCKS, and I'll take care of fixing that.
next prev parent reply other threads:[~2012-08-01 13:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-01 13:09 [Bug other/54150] New: " rguenth at gcc dot gnu.org
2012-08-01 13:12 ` [Bug other/54150] " rguenth at gcc dot gnu.org
2012-08-01 13:18 ` steven at gcc dot gnu.org [this message]
2012-08-03 8:22 ` steven at gcc dot gnu.org
2012-08-03 8:42 ` rguenth at gcc dot gnu.org
2012-08-06 11:44 ` steven at gcc dot gnu.org
2012-08-06 11:58 ` rguenth at gcc dot gnu.org
2012-09-19 14:15 ` rguenth at gcc dot gnu.org
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=bug-54150-4-UNltbNuxEd@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).