[Vm-dev] compiling the stack VM with LLVM at -Ofasty

[David T. Lewis]

On Thu, Oct 09, 2014 at 12:36:16PM -0700, John McIntosh wrote:
>  
> Ya, void is void not int  (a really old change set attached)

John, I checked this change set and I'm fairly sure that all of your
changes from voidIsVoidNotInt.cs have been incorporated in VMMaker.
I did not check the oscog branch for the stack interpreter, but given
the time stamps they are probably in both branches.

I have not heard any reports of a stack interpreter compiled in 64-bit
mode, so it is likely that there may be pointer/int issues that have not
been addressed in oscog. Eliot has done work to address method return
types (void versus int and so forth), so the oscog branch may be in
better shape in that regard.

Dave


> 
> On Thu, Oct 9, 2014 at 11:35 AM, Holger Hans Peter Freyther <
> holger at freyther.de> wrote:
> 
> >
> > On Thu, Oct 09, 2014 at 11:20:44AM -0700, Eliot Miranda wrote:
> >
> > > What's the bug?  The llvm folks claim their compiler passes the test
> > suites
> > > and is correct (but I'm not siding with them).  So I'm very curious...
> >
> > Well, a start would be to address the compiler warnings and compiler
> > errors (e.g. warnings about integer/long shifts, returning voide from
> > a method that should return int)
> >
> > I had already raised some of these points when building your cog
> > branch on FreeBSD with clang. In terms of system tools using the undefined
> > behavior sanitizer and address sanitizer might reveal some further
> > issues.
> >
> > cheers
> >         holger
> >
> 
> 
> 
> -- 
> ===========================================================================
> John M. McIntosh <johnmci at smalltalkconsulting.com>
> https://www.linkedin.com/in/smalltalk
> ===========================================================================