Guillermo Polito wrote:

> Pharo8 is pretty old :)

Hi Gulliermo,

Have you any stats on what are the most used Pharo version?

> The best I can propose is that you try compiling the VM without the JIT 
> compiler.
> That will not give you optimum performances, but acceptable ones compared to 
> Rosetta.
>
> I’d suggest you try to compile using the branch pharo-9. That’s probably the 
> oldest branch that is easy to build using cmake.
>
> If the pharo-9 branch does not work for your image, then maybe you should 
> check the branches (see the branches v8.x.x).
>
> For installation/build instructions, please follow the readme instructions. 
> If you find any issues, tell us, maybe there are cheap workarounds or fixes 
> :).

Thank you for your hints. I try to move the codebase to Pharo9, if it is too 
cumbersome then I try to compile the VM without JIT.

Cheers

Davide

> Hope that helps,
> Guille
>
> > El 6 ago. 2023, a las 22:07, stephane ducasse 
> > [stephane.duca...@inria.fr](mailto:stephane.duca...@inria.fr) escribió:
> >
> > > On 4 Aug 2023, at 20:24, Davide Varvello via Pharo-users 
> > > [pharo-users@lists.pharo.org](mailto:pharo-users@lists.pharo.org) wrote:
> > >
> > > Hi Guys,
> > > I want to use my old Pharo 8 image on an Apple Silicon (ARM64). I 
> > > downloaded the stable VM for apple silicon 
> > > http://files.pharo.org/get-files/110/pharo-vm-Darwin- 
> > > <http://files.pharo.org/get-files/110/pharo-vm-Darwin-arm64-stable.zip>arm64
> > >  
> > > <http://files.pharo.org/get-files/110/pharo-vm-Darwin-arm64-stable.zip>-stable.zip
> > >  <http://files.pharo.org/get-files/110/pharo-vm-Darwin-arm64-stable.zip> 
> > > but it isn't working with my pharo8 image.
> > >
> > > My old VM is working, of course, but I suppose it's because of Rosetta... 
> > > and the performance is not optimal.
> > >
> > > Any other solution?
> >
> > I do not think that we have a solution. I’m sorry but we decided that we 
> > cannot garantee that old Pharo version can run on Apple Silicon
> > just because of engineering effort.
> > With Pharo we are always trying not to trade the past for the future but 
> > this is difficult.
> >
> > S.

Reply via email to