[Coin-discuss] Optimization level for OsiClp, bug in pack1.mps

[Laszlo Ladanyi]

My mistake... I looked at Clp, not OsClp... D'oh!
Anyway, I have changed it to -O.

BTW, probably John Forrest would be the best to answer the following
philosophycal question: 
How important is it to compile OsiClp with -O? after all, the methods in it
should just invoke Clp, and maybe do a bunch of memory copying. And if both
Clp and Coin are compiled with -O, does it matter if OsiClp is compiled with
-g? Is there anything timeconsuming in the methods of OsiClp? (The same
question can be directed to ay other OsiXxx maintainer...)

--Laci

On Sat, 28 May 2005, Francois Margot wrote:

> >>
> >> Why is the default for compiling OsiClp set to -g instead of -O, like
> >> for all the other modules?
> >
> > I just checked it out and it's set to -O1...
> >
> 
> Call me crazy, but using a browser to the cvs repository at 14:00 EST
> Saturday, the first lines in COIN/Osi/OsiClp/Makefile are:
> 
> # Static or shared libraries should be built (STATIC or SHARED)?
> LibType := SHARED
> 
> # Select optimization (-O or -g). -O will be automatically bumped up to the 
> # highest level of optimization the compiler supports. If want something in
> # between then specify the exact level you want, e.g., -O1 or -O2
> OptLevel := -O
> OptLevel := -g
> 
> My understanding is that OptLevel will be set to -g.
> 
> Francois
> _______________________________________________
> Coin-discuss mailing list
> Coin-discuss at list.coin-or.org
> http://list.coin-or.org/mailman/listinfo/coin-discuss
>