On Thu, 18 Jul 2002 16:43:49 CDT, Jerry James said:
It is definitely a compiler bug. With gcc 2.95.3, using
"-mcpu=ultrasparc -O2" triggers the segfault. Using "-mcpu=ultrasparc
-O" gives the correct behavior.
The fact that the optimizer triggers it does not automatically mean it's
a compiler *bug*. I've seen instances where it *looked* like a compiler bug,
but in reality it was a program error with an aliasing issue - when running
without optimization, an otherwise dead store was concealing the bug. When
the optimizer was turned on, the dead store was removed, and the bug was
manifested.
--
Valdis Kletnieks
Computer Systems Senior Engineer
Virginia Tech