This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: egcs-2.92.02 19980905 (m68k-next-nextstep3): Address of hoisted load clobbered
- To: mark at markmitchell dot com
- Subject: Re: egcs-2.92.02 19980905 (m68k-next-nextstep3): Address of hoisted load clobbered
- From: Jeffrey A Law <law at cygnus dot com>
- Date: Wed, 09 Sep 1998 21:49:13 -0600
- cc: rth at cygnus dot com, toon at moene dot indiv dot nluug dot nl, egcs at cygnus dot com, egcs-patches at cygnus dot com
- Reply-To: law at cygnus dot com
In message <199809091850.LAA07837@smtp.earthlink.net>you write:
> But, when I reread the code, it didn't look to me like I "created" the
> MEM at all! See insert_loop_mem; it just takes a the MEM it's been
> handed, and stuffs it into the loop_mems array. Or are you reading my
> code better than me? (Which is entirely possible... :-( )
Right, but then you reference that MEM in two SET expressions that
you generate. One for the load, one for the store.
So we end up with two hunks of RTL which are sharing the MEM you
saved away.
jeff