[oi-dev] Optimize level O2 for libz

[stes@PANDORA.BE]

If there are tests for libz and if the tests do not fail, the O2 setting could be removed.

Ideally there exist tests that show why the O2 setting was/is being used.

In the case of Smalltalk Squeak I currently have a note in my Makefile

# override gcc_OPT (defaults to -O3) for the moment
# squeak compiles with -O2 or -O3 but
# KernelTests-Chronology with version 4.16.7 or 4.19.*
# gcc -O : 438 pass tests
# gcc -O2 : 20 failures 1 errors  #testAsDelay error
# the system compiled with -O3 / -O2 is usable but has Chronology failures
gcc_OPT=        -O


What exactly is the "maintainer meeting" ?

Regards,
David Stes

----- Op 12 okt 2021 om 15:34 schreef oi-dev oi-dev at openindiana.org:

> We discussed in the last maintainer meeting about the history of the O2 setting
> for build libz in OI. In the component build recipe is a note about problems
> with firefox if libz optimized in a higher level.
> I build libz without this restriction an tested with firefox 91.2.0esr. There I
> could not see any problems, so I suggest to remove the O2 setting for libz.
> --
> Carsten
> 
> _______________________________________________
> oi-dev mailing list
> oi-dev at openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev