Tru64 C optimisation

From: Gavin Kreuiter <gavin_at_transactive.usko.com>
Date: Sat, 25 Nov 2000 01:36:39 +0200

Hi managers, or, more precisely, C programmers, I guess.

I have a bit of a problem with about 160,000 lines of C code. When
compiling with standard options (default -O2), a particular input data file
generates "Program terminated with signal 11, Segmentation fault.". When
explicitly using -O0, the program completes as expected. I have looked at
the man page for cc options, but the exact optimising rules remain unclear.

My question is three-fold. Firstly, can anyone point me to documentation
describing the optimising steps of the compiler? Secondly, does anyone have
any experience in programming constructs that fail when the default
optimisation compiler option is selected, but succeed when no optimisation
is performed? And, finally, is this a problem with a faulty compiler, or
with bad programming practices that get understandably mangled by the
optimisation step?

I don't think the operating system release is relevant here, but, just in
case, we are running Digital UNIX V4.0D, with the latest 4.0D patches (I
think patch kit #3).

Tia
Gavin Kreuiter
Received on Sat Nov 25 2000 - 13:39:47 NZDT

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:41 NZDT