A gcc-cris bug?

[Tal Agmon]

Andrew Pinski wrote:

> Why it is fixed on the mainline already and for a good reason.  The
> RTL optimizations were just not good.  The tree level ones is where
> something like this gets fixed which is what happened, DOM (really
> only the copy progation part) and copy loop headers fixed the problem.
> There are many more places where things are fixed on the mainline for
> 4.0.0 which cannot be back ported to 3.x or 2.x.

If I understand you right, gcc-3.4.* final version will be releases with 
this 
bug. Do you have a workaround recommended for gcc-3.4.* users?