Loop unrolling -> stack corruption

[Allan Sandfeld Jensen]

On Wednesday 08 May 2002 19:35, Lubos Lunak wrote:
>
>  But this looks like a compiler bug to me. There shouldn't be any
> (functional) difference between code compiled with and without
> -funroll-loops. I even vaguely remember that older gcc versions had this
> switch buggy, making everybody put -fno-unroll-loops everywhere just in
> case (or was that -fno-strength-reduce? I don't remember).
It was strengt-reduce. Unroll-loops is not even activated by -O3 because it 
was experimental for a long time. I know there has been fixed bugs in 
unrolling for gcc 3.1, dont know whether they were introduced in 3.0 or are 
older.

>  Moreover I don't understand how broken kdeprint (whatever is wrong there)
> can cause crashes ten functions deeper.
Everything is possible.

greetings
`Allan