From: Paolo Bonzini <bonzini@gnu.org>
To: "\"Seongbae Park (???, ???)\"" <seongbae.park@gmail.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>,
Kenneth Zadeck <zadeck@naturalbridge.com>
Subject: Re: [PATCH] proper dataflow block visitation order
Date: Sat, 09 Feb 2008 14:11:00 -0000 [thread overview]
Message-ID: <47ADAE36.4080704@gnu.org> (raw)
In-Reply-To: <ab3a61990802081707p22da0980rda3d184f66963267@mail.gmail.com>
> Bootstrapped on i686 with c/c++ and no regression.
> While this is not exactly a regression,
> I'd like to commit this to 4.3 -
The patch may be okay for 4.3 with the changes Steven suggested.
However, I'd like to see also an assembly language output comparison for
some .i files (e.g. cc1 or SPEC).
Paolo
next prev parent reply other threads:[~2008-02-09 13:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-09 1:26 Seongbae Park (박성배, 朴成培)
2008-02-09 3:40 ` Kenneth Zadeck
2008-02-09 14:11 ` Paolo Bonzini [this message]
2008-02-09 16:07 ` Kenneth Zadeck
2008-02-09 16:11 ` Paolo Bonzini
2008-02-09 16:15 ` Kenneth Zadeck
2008-02-09 16:22 ` Paolo Bonzini
2008-02-09 16:39 ` Kenneth Zadeck
2008-02-10 22:36 ` Richard Guenther
2008-02-11 7:06 ` Mark Mitchell
2008-02-09 13:44 Steven Bosscher
2008-02-10 0:09 Bradley Lucier
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=47ADAE36.4080704@gnu.org \
--to=bonzini@gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=seongbae.park@gmail.com \
--cc=zadeck@naturalbridge.com \
/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).