[Pharo-dev] Tuning Opal Optimizations

Clément Bera bera.clement at gmail.com
Thu Nov 21 06:30:31 EST 2013


This mechanism does not work with Monticello.

On my builds I have for this case something similar to:


./pharo $JOB_NAME.image config $REPO ConfigurationOfMyProject
--install=bleedingEdge
./pharo $JOB_NAME.image eval --save 'SmalltalkImage compilerClass:
OpalCompiler. Compiler recompileAll.'



2013/11/21 Sven Van Caekenberghe <sven at stfx.eu>

>
> On 19 Nov 2013, at 16:45, Sven Van Caekenberghe <sven at stfx.eu> wrote:
>
> >>
> >> Yes, you can do it per class-hierarchy… you can implement on the class
> side a method to parametrize the compiler:
> >>
> >> compiler
> >>      ^super compiler options: #(- optionInlineTimesRepeat)
> >
> > Thanks, Marcus, that works just great.
>
> Marcus,
>
> Are we sure this option mechanism works when loading code through
> Monticello ?
>
> I mean, this build fails the PEGParser tests:
>
>   https://ci.inria.fr/pharo-contribution/job/Xtreams/
>
> but it includes the #compiler options in Xtreams-Parsing-nice.7
>
> Could it not be that this is a chicken-egg problem: the #compiler options
> are only there _after_ the class is loaded/compiled, or maybe it is an
> instance/class side problem ?
>
> Sven
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/attachments/20131121/34749c02/attachment-0002.html>


More information about the Pharo-dev mailing list