This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Infrastructure for MEM tracking
- To: Richard Kenner <kenner at vlsi1 dot ultra dot nyu dot edu>
- Subject: Re: Infrastructure for MEM tracking
- From: Jan Hubicka <jh at suse dot cz>
- Date: Mon, 1 Oct 2001 14:16:01 +0200
- Cc: gcc-patches at gcc dot gnu dot org
- References: <10110011136.AA05622@vlsi1.ultra.nyu.edu>
> This patch adds a new data structure that contains information about
> a MEM. Right now, only the alias set is actually used, so no functional
> change is occurring.
Nice I was quite impatiently waiting for this patch as I would like to do some
working that depdends on this bits. Thanks!
But I do have different question. How much work would be to make your approach
to work for hard registers too? I would like to track some information after
reload (currently we do track the original pseudo, but I would like to track
original pseudo and the offset when it is split to multiple registers, so
we can update the debug information after register renaming or live range
splitting is done).
Also the code in depdendence.c currently abuses another field of MEM RTX.
We probably should to move that one into the new datastructure too.
Also it would be nice to see the information visualized by print_rtx.
I will probably try to implement these sometime in future if no one is faster.
Honza