From: Brad Lucier <lucier@math.purdue.edu>
To: jh@suse.cz (Jan Hubicka)
Cc: lucier@math.purdue.edu (Brad Lucier),
gcc-patches@gcc.gnu.org, rth@cygnus.com, jh@suse.cz,
gcc@gcc.gnu.org
Subject: Re: Timing information for CFG manipulations
Date: Wed, 17 Oct 2001 12:43:00 -0000 [thread overview]
Message-ID: <200110171943.f9HJh3420750@banach.math.purdue.edu> (raw)
In-Reply-To: <20011016170137.D32633@atrey.karlin.mff.cuni.cz>
> I don't have time to finish bootstrap, but the patch appears to work.
> OK assuming the bootstrapping/regtesting i386 passes fluently?
>
> Honza
>
> Tue Oct 16 16:56:33 CEST 2001 Jan Hubicka <jh@suse.cz>
> * basic-block.h (find_sub_basic_blocks): Use sbitmap parameter.
> * cfgbuild.c (find_bb_boundaries): Break out from ...
> (find_sub_basic_blocks): ... here; reorganize to handle multiple
> basic blocks at once.
> * cfgrtl.c (commite_one_edge_insertion): Create an bitmap to pass
> to find_sub_basic_blocks.
> * recog.c (split_all_insns): Update find_sub_basic_blocks call.
I haven't seen this patch approved or acknowledged yet, but if it helps, I
bootstrapped and regtested it on i686-pc-linux-gnu, see
http://gcc.gnu.org/ml/gcc-testresults/2001-10/msg00245.html
Brad
next prev parent reply other threads:[~2001-10-17 12:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-13 20:33 Brad Lucier
2001-10-13 21:53 ` Zack Weinberg
2001-10-15 11:58 ` Brad Lucier
2001-10-16 21:15 ` Zack Weinberg
2001-10-15 12:54 ` Brad Lucier
2001-10-15 14:18 ` Daniel Berlin
2001-10-14 1:18 ` Jan Hubicka
2001-10-14 8:46 ` Brad Lucier
2001-10-14 9:21 ` Daniel Berlin
2001-10-16 7:22 ` Jan Hubicka
2001-10-16 8:25 ` Brad Lucier
2001-10-16 12:46 ` Richard Henderson
2001-10-16 8:01 ` Jan Hubicka
2001-10-16 12:39 ` Brad Lucier
2001-10-16 14:45 ` Jan Hubicka
2001-10-16 16:57 ` Brad Lucier
2001-10-17 12:43 ` Brad Lucier [this message]
2001-10-17 13:38 ` Richard Henderson
2001-10-17 14:00 ` Jan Hubicka
2001-10-17 15:38 ` Jan Hubicka
2001-10-17 16:10 ` Richard Henderson
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=200110171943.f9HJh3420750@banach.math.purdue.edu \
--to=lucier@math.purdue.edu \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=jh@suse.cz \
--cc=rth@cygnus.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).