[omniORB] CORBA::Double corrupted when compiling -O2 and -O3

[Ciprian Enache]

Hello Stuart,

I've noticed a similar problem when connecting from with an Omniorb 
python client to an ORBACUS server, but I thought it was caused by some 
incompatibility in the interface layer.

Running on Debian Testing.

Best regards,
Ciprian Enache
Stuart Caunt wrote:
> Hi,
>
> I've recently upgraded my linux system and have noticed that values passed
> as CORBA::Double in our CORBA application are not passed correctly - the
> values end up being very close to zero, eg 1.213342e-41 for all values
> (even if they were originally 1.2, 3.4, 10.0, etc).
>
> We've traced the root of the problem to the optimisation flag. Originally
> it was -O3 but even at -O2 the problem remains. -O1 removes the problem. I
> understand that -O3 can have certain effects on the reliability of
> floating point calculations but I'm more surprised at the -O2 optimisation
> problem.
>
> I'm running on Debian Etch with OmniORB 4.0.6 and g++ 4.1.2. Has anyone
> else had similar problems?
>
> Many thanks,
> Stuart
>
>
> _______________________________________________
> omniORB-list mailing list
> omniORB-list at omniorb-support.com
> http://www.omniorb-support.com/mailman/listinfo/omniorb-list
>
>   


-- 
Ciprian Enache
Computaris Ltd
E-mail: Ciprian.Enache at computaris.com
Office: +40-21-204-5225
Mobile: +40-726-743-510


This email is subject to Computaris email terms of use: http://www.computaris.com/email_terms.html