On 8/10/2011 4:12 PM, michael_rytting_at_agilent.com wrote:
> It is set to 1
> On Aug 10, 2011, at 3:51 PM, "Philip Martin"<philip.martin_at_wandisco.com> wrote:
>> <michael_rytting_at_agilent.com> writes:
>>> If I disable optimizations by doing "make CFLAGS=-O0" the program no
>>> longer crashes.
>> That suggests it could be a compiler bug.
Sorry to jump in so late, but I had significant problems with
optimization for 64-bit executables under CentOS 4.x. If you can't
upgrade, I suggest dialing down the optimization flags. I had to drop
from -O3 to -O2 so that Crypto++ 5.5.2 would run, for example. At some
point I could drop support for RHEL/CentOS 4.x from my client's products
and try going back to -O3, but the required testing hasn't been real
high on the priority list.
Assuming the SVN configuration scripts can distinguish between the
releases, I suspect that changing the default optimization flags for
RHEL 4.x will be simpler than trying to fix the new UTF-8 code. Have
you tried intermediate levels of optimization? We went to production
with -O2, so it's not as if all 64-bit optimizations were broken.
David Chapman dcchapman_at_acm.org
Chapman Consulting -- San Jose, CA
Received on 2011-08-11 01:43:57 CEST