openexr-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Openexr-devel] Visual Studio 2k5 beta 2 generates 1000 warningscomp


From: Luc-Eric Rousseau
Subject: RE: [Openexr-devel] Visual Studio 2k5 beta 2 generates 1000 warningscompiling OpenEXR...
Date: Tue, 30 Aug 2005 15:57:11 -0400

We ship a Win64 app with OpenEXR,
and mental images probably uses it 
as well on their side.

------------------
Luc-Eric Rousseau
Team Leader, User Interface
Softimage|XSI


> -----Original Message-----
> From: address@hidden
> [mailto:address@hidden Behalf
> Of Florian Kainz
> Sent: Tuesday, August 30, 2005 3:04 PM
> To: Bob Friesenhahn
> Cc: Granthill Granthill; address@hidden
> Subject: Re: [Openexr-devel] Visual Studio 2k5 beta 2 generates 1000
> warningscompiling OpenEXR...
> 
> 
> Bob Friesenhahn wrote:
> > On Tue, 30 Aug 2005, Florian Kainz wrote:
> > 
> >> Don't panic.  We have known for a while that Visual Studio likes
> >> to complain about our code, we have looked at the warnings, and we
> >> will eventually fix them.  We have tested the code extensively, and
> >> it does run fine in 32-bit and 64-bit environments.  Most of the
> >> warnings flag either problems that are of a more theoretical nature
> >> or things that are not actually problems.
> > 
> > I am glad to hear that the OpenEXR code works well at 64-bits on an 
> > Itanium CPU running Windows and 64-bit 'x86 Windows.  If so, then 
> > OpenEXR must be much better prepared than the vast majority 
> of existing 
> > software packages.  I have not yet tried my own code in those 
> > environments, but although it works great at 64-bits on 
> other systems 
> > (SGI, Compaq Alpha, AMD Opteron with Linux, UltraSPARC) I 
> expect it to 
> > go "kersplat" as a 64-bit Windows program.
> > 
> > Some Microsoft compiler warnings are simply annoying.  It seems that
> > 
> >   pragma warning( disable: 4800 )
> > 
> > should eliminate the silly warning about bool conversions.
> > 
> 
> Let me qualify this... we've tested OpenEXR on 32-bit and 64-bit
> Linux (on X86-64, not Itanium), and on 32-bit Windows.  As far
> as we know, we don't rely on "long" being the same size as a
> pointer.  In a few places, where we really need 64-bit integers,
> we use Int64, which is defined as "unsigned __int64" on Windows.
> 
> 
> _______________________________________________
> Openexr-devel mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/openexr-devel
> 




reply via email to

[Prev in Thread] Current Thread [Next in Thread]