[Bf-committers] Re: Compiling blender on OS X 10.3

[Charles Wardlaw]

Hi,

Out of curiosity, does adding the G5 flags cause the compiler to
generate 64-bit code, or just 32-bit code optimised for the G5?

And as I'm running on a G3 iBook here, I would like to say that code
optimised for a G4 *does* tend to run slower on the G3.  Games are
extremely notorious for this.  I know this is asking a bit much, but it
might be nice to have separate versions for separate compilers, not
unlike Peak.

- Charles

--- Michael Velikanje <mikev@gci.net> wrote:
> 
> > --__--__--
> >
> > Message: 5
> > From: Stefan Gartner <stefang@aon.at>
> > To: bf-committers@blender.org
> > Subject: Re: [Bf-committers] Re: Compiling blender on OS X 10.3
> > Date: Wed, 29 Oct 2003 09:40:29 +0100
> > Reply-To: bf-committers@blender.org
> >
> > On Wednesday 29 October 2003 06:52, Michael Velikanje wrote:
> >> Ok I lied, setting -mcpu=G4 -fast does work for compiling
> >> QUICKTIME=true on 10.3 the same as it did on 10.2. Like:
> >>
> >> ifeq ($(OS),darwin)
> >>      CC	= gcc
> >>      CCC	= g++
> >>      CFLAGS	+= -pipe -fPIC -mcpu=G4 -fast
> >>      CCFLAGS	+= -pipe -fPIC -mcpu=G4 -fast
> >> <<
> >> Every thing that I've tried works great :^)
> >
> > Thanks for the tip! Do you happen to know if binaries compiled with
> 
> > -mcpu=G4
> > work on G3 machines, or alternatively, does it work with -fast
> alone? 
> > I don't
> > have 10.3, so I can't test it myself.
> >
> > sgefant
> >
> The -mcpu=G4 flag is for use in conjunction with -fast, there is a 
> second flag -mtune=G4 that is also for use with -fast, they actually 
> unset a flag that is set by default.
> -fast sets:
>  >>
> -O3
> -falign-loops-max-skip=15
> -falign-jumps-max-skip=15
> -falign-loops=16
> -falign-jumps=16
> -falign-functions=16
> -malign-natural
> -ffast-math
> -fstrict-aliasing
> -frelax-aliasing
> -fgcse-mem-alias
> -funroll-loops
> -floop-transpose
> -floop-to-memset
> -finline-floor *
> -mcpu=G5 *
> -mpowerpc64
> -mpowerpc-gpopt
> -mtune=G5 **
> -fsched-interblock
> -fload-after-store
> --param max-gcse-passes=3
> -fno-gcse-sm
> -fgcse-loop-depth
> -funit-at-a-time
> -fcallgraph-inlining
> -fdisable-typechecking-for-spec
> * These flags are not set if the -mcpu=G4 flag is used in conjunction
> 
> with -fast.
> ** This flag is not set if the -mtune=G4 flag is used in conjunction 
> with -fast.
> <<
> -fast is probably only for G4 G5s since it doesn't list a G3 flag. I 
> have found one problem, some times opening the file select window 
> causes blender to crash, but not every time, I'm trying to figure out
> 
> what the difference is between it working and not. As for binary's
> that 
> are compiled on a G4 with -fast set working on a G3........??? that
> is 
> a good question. I could e-mail the binary (package) if you're using
> a 
> G3 (9.5meg it will compress some though). I just compiled the 
> blender230 CVS, and the file select windows work every time now. f-11
> 
> does have some strange behavior though, the render window goes away
> but 
> so does the main blender window.
> 
> Michael Velikanje
> 
> _______________________________________________
> Bf-committers mailing list
> Bf-committers@blender.org
> http://www.blender.org/mailman/listinfo/bf-committers