[Vm-dev] cute, we crash gcc...

Tobias Pape Das.Linux at gmx.de
Tue Mar 20 19:33:00 UTC 2018


Hi 

> On 20.03.2018, at 16:27, Eliot Miranda <eliot.miranda at gmail.com> wrote:
> 
> Hi Tobias, Hi Ryan,
> 
> On Tue, Mar 20, 2018 at 6:12 AM, Tobias Pape <Das.Linux at gmx.de> wrote:
> 
> On 20.03.2018, at 13:58, Holger Freyther <holger at freyther.de> wrote:
>> 
>> 
>> 
>> 
>>> On 20. Mar 2018, at 11:54, Tobias Pape <Das.Linux at gmx.de> wrote:
>>> 
>> 
>> Hey!
>> 
>> 
>>> https://travis-ci.org/OpenSmalltalk/opensmalltalk-vm/jobs/355802605#L2458
>> 
>> indeed! I think it is this bug: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59477. I love how GCC developers add a regression test for every issue fixed and they do it for many many years already. And it is a codebase that is 30+ years old and started before SSA was "known".
> 
> Yes, upgrading GCC fixes this (see https://travis-ci.org/OpenSmalltalk/opensmalltalk-vm/builds/355826629 )
> 
> But the newspeak-bootstrap now fails.
> 
> @Eliot, can you have a look at this?
>        https://travis-ci.org/OpenSmalltalk/opensmalltalk-vm/jobs/355826630#L6518
> I actually cannot fathom how a gcc upgrade should influence this, but I'll hold whit the Pull Request until you say that its either my fault or nothing to be afraid of.
> 
> Well, if it's a result of my enabling read-only objects (-DIMMUTABILITY=1) for all Spur VMs then I'll turn it off for the Newspeak builds, but the key point here is that we should decouple the Newspeak builds from the Pharo and Squeak builds asap.  Newspeak shouldn't block new releases of what should be perfectly good VMs.  This is urgent IMO.

Ok I'll see,
but two things:

First, it works for 32bit but not 64bit.

Second, the Newspeak build did not get the added -DIMMUTABILITY=1, so it is probably not that…

Any other suggestions?


Best regards
	-Tobias

> 
> _,,,^..^,,,_
> best, Eliot



More information about the Vm-dev mailing list