public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/54150] New: [4.8 Regression] gimple dumps no longer honor -blocks
Date: Wed, 01 Aug 2012 13:09:00 -0000	[thread overview]
Message-ID: <bug-54150-4@http.gcc.gnu.org/bugzilla/> (raw)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54150

             Bug #: 54150
           Summary: [4.8 Regression] gimple dumps no longer honor -blocks
    Classification: Unclassified
           Product: gcc
           Version: 4.8.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: other
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: rguenth@gcc.gnu.org
                CC: stevenb.gcc@gmail.com


gimple dumps now by default dump a RTL-like bb header:

;;   basic block 2, loop depth 0
;;    pred:       ENTRY
  D.1602_12 = (sizetype) m_5(D);
  D.1603_13 = D.1602_12 * 4;
  goto <bb 6>;

;;    succ:       6

previously TDF_blocks was required for that (and I'd like to have that back).
Also notice the extra newline before ;; succ: which seems to be caused by
pp_base_flush which does not only flush but also prints a newline, and that
independent on whether pp_needs_newline is set.

That said, the tree dumps still look remarkably ugly by default now.


             reply	other threads:[~2012-08-01 13:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-01 13:09 rguenth at gcc dot gnu.org [this message]
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
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@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).