This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: RFC: support for multiple CFGs (necessary for the tree-profiling branch)
- From: Richard Henderson <rth at redhat dot com>
- To: Steven Bosscher <stevenb at suse dot de>
- Cc: gcc at gcc dot gnu dot org, stuart at apple dot com, Jan Hubicka <jh at suse dot cz>
- Date: Mon, 24 May 2004 09:38:00 -0700
- Subject: Re: RFC: support for multiple CFGs (necessary for the tree-profiling branch)
- References: <200405232300.29835.stevenb@suse.de>
On Sun, May 23, 2004 at 11:00:29PM +0200, Steven Bosscher wrote:
> +#define ENTRY_BLOCK_PTR(FN) ((FN)->cfg->entry_block_ptr)
> +#define EXIT_BLOCK_PTR(FN) ((FN)->cfg->exit_block_ptr)
> +#define BASIC_BLOCK_INFO(FN) ((FN)->cfg->basic_block_info)
> +#define N_BASIC_BLOCKS(FN) ((FN)->cfg->n_basic_blocks)
> +#define N_EDGES(FN) ((FN)->cfg->n_edges)
> +#define LAST_BASIC_BLOCK(FN) ((FN)->cfg->last_basic_block)
> +#define LABEL_TO_BLOCK_MAP(FN) ((FN)->cfg->label_to_block_map)
It would seem to be an easier change to imply cfun in these macros
and to use a separate set (or none at all) for the rare case of
having to access a different function's cfg.
r~