Hi David, I'm on Mac OS X 10.11 with Xcode 8.2 (Apple LLVM 8.0) [1]. When I build latest Poly/ML sources with "--enable-compact32bit" (no others), when I execute "make compiler" (after "make"), with large chances I get the following error:
... Created functor TYPECHECK_PARSETREE Making MATCH_COMPILER Making MatchCompilerSig Created signature MatchCompilerSig Created functor MATCH_COMPILER Making CODEGEN_PARSETREE Making CodegenParsetreeSig Created signature CodegenParsetreeSig Created functor CODEGEN_PARSETREE Making PARSE_TREE Created functor PARSE_TREE Assertion failed: (space != 0), function ScanObjectAddress, file quick_gc.cpp, line 414. /bin/sh: line 1: 96770 Abort trap: 6 ./poly --error-exit < mlsource/BuildExport.sml make: *** [compiler] Error 134 The same error message (Assertion failed: (space != 0), function ScanObjectAddress, file quick_gc.cpp, line 414.) also happens multiple times (but random) when I was trying to build HOL4. Without "--enable-compact32bit" (normal 64-bit build), everything is fine. Such an issue must be new since the last time I tested PolyML after your announcement (of "--enable-compact32bit") in the mailing list. Hope this helps, Chun Tian [1] compiler information: Apple LLVM version 8.0.0 (clang-800.0.42.1) Target: x86_64-apple-darwin15.6.0 Thread model: posix InstalledDir: /Library/Developer/CommandLineTools/usr/bin Il 21/02/19 13:44, David Matthews ha scritto: > The current version of Poly/ML is approaching the point of creating a > new release, 5.8. Makarius has run a lot of tests with Isabelle and > various bugs have been fixed. This has mainly affected the 32-bit > object ID version for 64-bits but some of the fixes will also have > affected the native-address versions. > > This is a last chance to test the current git master before release. > Don't forget to run "make compiler" at least twice after the initial > "make" in order to build the up-to-date compiler and recompile all the > code with it. This is particularly important if testing the > --enable-compact32bit version. Some extra checking was added during > testing and there is a strong chance of getting an assertion failure > during the initial "make" or the first "make compiler" due to a bug in > the pre-built compiler. If this happens just rerun the step. Once the > compiler has been rebuilt it will incorporate a fix. > > David > > _______________________________________________ > polyml mailing list > polyml@inf.ed.ac.uk > http://lists.inf.ed.ac.uk/mailman/listinfo/polyml
signature.asc
Description: OpenPGP digital signature
_______________________________________________ polyml mailing list polyml@inf.ed.ac.uk http://lists.inf.ed.ac.uk/mailman/listinfo/polyml
