From: Alexander Monakov <amonakov@ispras.ru>
To: Vladimir Makarov <vmakarov@redhat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PING][PATCH]: Allow CFG with empty BBs in selective scheduler
Date: Tue, 28 Apr 2009 10:24:00 -0000 [thread overview]
Message-ID: <20090428101211.GE3381@endeed2.ispras.ru> (raw)
In-Reply-To: <49F1FC31.5090907@redhat.com>
On Fri, Apr 24, 2009 at 01:51:45PM -0400, Vladimir Makarov wrote:
> Please, only merge two changelog entries for sel-sched-ir.c into one:
>
> * sel-sched-ir.c (maybe_tidy_empty_bb): Do not attempt to delete a
> block if there are complex incoming edges.
> (sel_merge_blocks): Remove useless assert.
> (sel_redirect_edge_and_branch): Check that edge was redirected.
> * sel-sched-ir.h (_eligible_successor_edge_p): Remove assert.
> (sel_find_rgns): Delete declaration.
>
Retested on ia64-linux, committed to trunk as revision 146882. Sorry, but I
left the changelog unchanged: the second entry is for .h file, not .c.
Thanks.
--
Alexander Monakov
prev parent reply other threads:[~2009-04-28 10:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-31 12:21 [PATCH]: " Alexander Monakov
2009-01-26 0:04 ` [PING][PATCH]: " Alexander Monakov
2009-04-24 18:25 ` Vladimir Makarov
2009-04-28 10:24 ` Alexander Monakov [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=20090428101211.GE3381@endeed2.ispras.ru \
--to=amonakov@ispras.ru \
--cc=gcc-patches@gcc.gnu.org \
--cc=vmakarov@redhat.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).