Hi,
On Tue, 6 Mar 2007, Joern Rennecke wrote:
> In http://gcc.gnu.org/ml/gcc/2007-03/msg00128.html, you wrote:
> > One case is about multiple increments, the tree optimizer merges them and
> > increments the register only once, so if one only looks at the size of the
> > pointer value one misses
In http://gcc.gnu.org/ml/gcc/2007-03/msg00128.html, you wrote:
> One case is about multiple increments, the tree optimizer merges them and
> increments the register only once, so if one only looks at the size of the
> pointer value one misses them, e.g. something like this:
>
> (set (mem (reg
On Mon, Mar 05, 2007 at 03:44:20AM +0100, Roman Zippel wrote:
> The dataflow porting document mentions other possible, but doesn't mention
> any examples. Anything I might have to look out for regardings the m68k
> post_inc/pre_dec addressing modes?
I have not checked what GCC currently gen
> Hi,
>
> I'mm currently looking at the dataflow branch for m68k mainly because of
> the new auto-inc-dec pass, I worked a bit on the old code in flow.c, but
> considering the new pass, I think it doesn't make much sense to continue
> it.
>
I agree. Wit
Hi,
I'mm currently looking at the dataflow branch for m68k mainly because of
the new auto-inc-dec pass, I worked a bit on the old code in flow.c, but
considering the new pass, I think it doesn't make much sense to continue
it.
I'm attaching my current patch and some test ca
