http://bugs.freedesktop.org/show_bug.cgi?id=24650





--- Comment #8 from Karl Schultz <karl.w.schu...@gmail.com>  2009-11-03 
12:20:32 PST ---
Yeah, I'm preparing a set of changes to allow Mesa 7.6 to build on Visual
Studio.  Right now, the 7.6 tarballs do not build.

And I'm sitting here watching the image code compile for a LONG time.

I think I can put this at the top of the file:

#if _MSC_VER == 1400
#pragma optimize("", off)
#endif

This may also work and only turns off global optimizations, which I am
guessing is the issue here.  I'll have to experiment.

#if _MSC_VER == 1400
#pragma optimize("g", off)
#endif

and that should not be too horrible.  But I do hate putting MSFT hacks like
this in the source.

I don't see a good way to turn off the optimization for this file by using
only the build files (Visual Studio project files).  We ship VC8 (the 2005
compiler) project files.  People with VC9 (the 2008 compiler) convert the
VC8 files to VC9 when they load them.  This lets us maintain only one
version to support 2005 and 2008.  If we moved to shipping separate VC8 and
VC9 project files, we could turn off the optimizer in the mesa Project file
for the file(s) in question, but that would be the only difference between
the two versions.  I'm not sure that is worth doing because it is hard
enough keeping one set of project files up to date.

I'll work on it a bit more and submit the appropriate patches.

Karl


On Mon, Nov 2, 2009 at 11:06 AM, <bugzilla-dae...@freedesktop.org> wrote:

> http://bugs.freedesktop.org/show_bug.cgi?id=24650
>
>
>
>
>
> --- Comment #7 from Ian Romanick <i...@freedesktop.org>  2009-11-02
> 10:06:31 PST ---
> (In reply to comment #6)
> > I've seen the older (2005) compilers take a long time to compile one the
> > files, image.c I think, in 32-bit Release mode.  I think that this source
> > code file used a lot of macros that expanded out to a lot of code.  And
> this
> > code's size or structure caused the optimizer to take a long time to
> build
> > it.
> >
> > I worked around it in the 2005 studio by turning off optimization just
> for
> > that one file.  I have not noticed the problem with the 2008 tools.
>
> Perhaps we could use some #ifdef to detect Visual Studio 2005 and disable
> optimization via a #pragma?
>
>
> --
> Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You are the assignee for the bug.
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Mesa3d-dev mailing list
> Mesa3d-dev@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
>


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Mesa3d-dev mailing list
Mesa3d-dev@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mesa3d-dev

Reply via email to