On Fri, 6 Apr 2001, Juergen Vigna wrote:
> Well it seems very strange that this does not happen with egcs 2.91.66 and
> also does not happen if you omit -O (no optimization), for me this seems like
> a bug in the 2.96.x compiler when optimizing!
>
> Jürgen
Quite possibly. I wonder if the same problem is on the CVS gcc 3.0 branch. If it really
is a compiler bug, I imagine they will be interested.
Why does the crash happen ? A pointer gone astray ? I didn't look at the backtrace
for long.
I don't support -fno-strict-aliasing will help ?
john
--
"I am a conscientious man, when I throw rocks at seabirds I leave no tern
unstoned."
- Ogden Nash
