[L2Ork-dev] two optimization flags

Ivica Ico Bukvic ico at vt.edu
Thu May 31 16:53:42 EDT 2018


Leftover from the legacy build? I know I added O6 at one point to 
optimize freeverb~. That said, I may have done this only in the 
freeverb~ makefile (but am not 100% sure this is the case). Perhaps 
github commits may shine some clarity on this?


On 5/31/2018 10:26 AM, Jonathan Wilkes wrote:
> On Wed, May 30, 2018 at 6:00 PM, Giulio Moro <g.moro at qmul.ac.uk> wrote:
>> I think O6 just does not exist for gcc and clang, so possibly it reverts to O3?
>>
>> https://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html
> Ok, so from that doc:
>
> "If you use multiple -O options, with or without level numbers, the
> last such option is the one that is effective."
>
> That means we're currently getting whatever optimization level -O6
> ends up triggering, and
> the initial -O2 is ignored.
>
> So... why is there a leading "-O2" optimization flag?
>
> -Jonathan
> _______________________________________________
> L2Ork-dev mailing list
> L2Ork-dev at disis.music.vt.edu
> https://disis.music.vt.edu/listinfo/l2ork-dev



More information about the L2Ork-dev mailing list