This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: should MEM tracking be able to optimize this?
- From: Dan Nicolaescu <dann at godzilla dot ICS dot UCI dot EDU>
- To: Richard Kenner <kenner at vlsi1 dot ultra dot nyu dot edu>
- Cc: gcc at gcc dot gnu dot org
- Date: Fri, 16 Nov 2001 15:02:29 -0800
- Subject: Re: should MEM tracking be able to optimize this?
- References: <10111162059.AA25024@vlsi1.ultra.nyu.edu>
Richard Kenner <kenner@vlsi1.ultra.nyu.edu> writes:
"calc1" one has too many loads and stores... Should MEM tracking be
able to dissambiguate the non-dependend loads and stores in "calc1"?
No, only in calc2. The point is that it can now disambiguate when you
have separate variables, like you do in calc2. In calc1, what you
have are different *fields* of the same variable and that isn't what
is tracked.
Do you have any plans to do anything about tracking the fields too?
Or it's not considered to be worth the effort?