[Vm-dev] CMakeMaker--whaddya think?

[Igor Stasenko]

On 17 April 2014 00:59, Esteban Lorenzano <estebanlm at gmail.com> wrote:

>
> yeah, that script does not fails for me :(
>
> you should have transcript window opened.
it doesn't fails if it closed..

which, btw a good sign where the problem might be hiding - in process
switching code.

On 16 Apr 2014, at 20:33, Nicolas Cellier <
> nicolas.cellier.aka.nice at gmail.com> wrote:
>
>
> 2014-04-16 19:13 GMT+02:00 Eliot Miranda <eliot.miranda at gmail.com>:
>
>>
>>
>>
>>
>> On Wed, Apr 16, 2014 at 9:58 AM, Nicolas Cellier <
>> nicolas.cellier.aka.nice at gmail.com> wrote:
>>
>>>
>>>
>>> 2014-04-16 18:48 GMT+02:00 Esteban Lorenzano <estebanlm at gmail.com>:
>>>
>>>>
>>>>
>>>> On 16 Apr 2014, at 18:33, Nicolas Cellier <
>>>> nicolas.cellier.aka.nice at gmail.com> wrote:
>>>>
>>>>
>>>> 2014-04-16 14:38 GMT+02:00 Göran Krampe <goran at krampe.se>:
>>>>
>>>>>
>>>>> Hey!
>>>>>
>>>>> On 04/16/2014 01:22 PM, gettimothy wrote:
>>>>>
>>>>>> Hi Estaban,
>>>>>>
>>>>>>
>>>>>>  >>Is a bit frustrating so I will say it again: CMakeMaker already
>>>>>> does
>>>>>> that. And it does it for *any* vm flavour (we are generating pharovm
>>>>>> because that’s what we are using, but the builders for cog, stack and
>>>>>> even interpreter are there, and working… bah the interpreter version
>>>>>> needs >>some work).
>>>>>>   >>Nothing prevents you to copy the pharo flavour and adapt it as
>>>>>> squeak flavour.
>>>>>>   >>Nothing prevents you to do the same for newspeak.
>>>>>>
>>>>>>   >>cheers,
>>>>>>   >>Esteban
>>>>>>
>>>>>>   >>ps: Thanks Dave for noticing :)
>>>>>>
>>>>>> I did not know that project existed;  of course I will start with that
>>>>>> and with the existing Interpreter stuff Dave mentioned.
>>>>>>
>>>>>> Its is refreshing to know my instincts on how to approach the project
>>>>>> where correct! Heck, we even came up with the same name for it!
>>>>>>
>>>>>
>>>>> Just wanted to mention that at 3DICC we are in the process of moving
>>>>> over to the Pharo build system for our client side (OSX and Windows) VMs.
>>>>>
>>>>> Just a reflection: It was quite easy to get started, finding a proper
>>>>> place to add 3DICC subclasses, adding in methods for our plugins etc. I got
>>>>> distracted by other things but now I am picking up our OSX build again so
>>>>> soon we should be using it for real.
>>>>>
>>>>> And also, it builds fine with clang! Thanks Esteban :)
>>>>>
>>>>> regards, Göran
>>>>>
>>>>
>>>> BEWARE: it builds fine, but the resulting VM behaves weirdly : see
>>>>
>>>> https://pharo.fogbugz.com/f/cases/11130/Special-byte-code-sequences-mess-up-the-stack-of-VM
>>>>
>>>>
>>>> that’s a real strange case, that does not happens all the time (in
>>>> fact, that’s one of the problems we have: it is hard to have a reproducible
>>>> case),
>>>>
>>>>
>>> For me, the ssnippet from Stephan Eggermont works reliably well
>>> (I mean allways fails in official 3.0 distribution for MacOSX )
>>>
>>> 1 to: 1000 do: [ :i |
>>>         | string |
>>>         Transcript show: 'Iteration '; show: i; cr.
>>>         1 timesRepeat: [
>>>             (string := String new: 1000 withAll: $a)
>>>                 reversed.
>>>         ].
>>>     ].
>>>
>>> When Transcript is opened, I never reached iteration 1000 on my mac with
>>> official VM.
>>> There's always an Integer that does not understand reversed in my way.
>>>
>>
>> Hence to get a rep[roducible case, that you could even look at in the
>> Simulator, merely evaluate
>>
>> Smalltalk snapshot: true andQuit: true.
>> 1 to: 1000 do: [ :i |
>>         | string |
>>         Transcript show: 'Iteration '; show: i; cr.
>>         1 timesRepeat: [
>>             (string := String new: 1000 withAll: $a)
>>                 reversed.
>>         ].
>>     ].
>>
>> and when you start-up the image it should crash with no user
>> intervention.  Voila, a reproducible case...
>>
>>
> If the problem is the compiler, or a compielr flag, can the simulator find
> the problem?
> My understanding is that the simulator is going to emulate slang, and
> eventually jitted code.
> But the slang is AFAICT correct (with another compiler/flags the problem
> vanishes)...
>
> Nicolas
>
>
>>
>>>
>>>> Either we are back to disecting correct set of gcc/clang flags
>>>> Or we shall revert to an older gcc (4.2.1 works for me OSX 10.6.8 Xcode
>>>> 3.2.6)
>>>>
>>>> Nicolas
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>> --
>> best,
>> Eliot
>>
>>
>
>
>


-- 
Best regards,
Igor Stasenko.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/vm-dev/attachments/20140417/5af53631/attachment.htm