The VM included in the 5.3 package for the ARM linux systems is fatally broken due to a code generator bug; we had various discussions about the issue in mid-March. We also noticed a problem with the bitBLT code for all platforms that was fixed by VMMaker.oscog-nice.2732
We really need to push the magic buttons to replace the ARM package in order for it to run at all; updating the other platforms to fix bitBLT would be nice. A quick test of the next available VM on bintray suggests that the https://bintray.com/opensmalltalk/vm/download_file?file_path=squeak.cog.spur_linux32ARMv6_202003291024.tar.gz version is functional - but maybe we want to use the latest? What needs doing to solve this for the download page? tim -- tim Rowledge; [hidden email]; http://www.rowledge.org/tim Useful random insult:- On permanent leave of absence from his senses. |
On Mon, Apr 20, 2020 at 8:39 AM Marcel Taeumel <[hidden email]> wrote:
Can we please use CoInterpreter VMMaker.oscog-eem.2741 uuid: 809e8b1f-fe07-4d33-bfc1-db9e5ab13a99 Apr 15 2020 StackToRegisterMappingCogit VMMaker.oscog-eem.2739 uuid: b15f5d3d-0493-4edc-a9d3-4775bb9a21e5 Apr 15 2020 VM: 202004192151 CommitHash: 6e5241e ? This has this one change that I'd like to be in the VM: Spur: Make sure that becomeForward: answers a useful error code for read-only targets (when copyHash is true).
_,,,^..^,,,_ best, Eliot |
Hi Eliot. > Can we please use ... 202004192151 ... Let's start running some tests with on this one. Best, Marcel
|
Hi Marcel, On Tue, Apr 21, 2020 at 6:10 AM Marcel Taeumel <[hidden email]> wrote:
Things are pretty stable. There was one major change to how the VM moves from machine code into the interpreter, replacing a setjmp/longjmp pair with a much lighter-weight "jump-call with substituted return address". But this "just works". We're able to perform experments without disturbinf=g trunk. SO for example, adding makefiles to allow building of the VM under clang-cl.exe on Windows was done without affecting the other builds at all.
_,,,^..^,,,_ best, Eliot |
Hi Eliot, thank you. That's good news. :-) Best, Marcel
|
Hi all! I will now test 202004292351 as a release candidate for a new VM release to be also used in Squeak 5.3 to fix ARM support. Best, Marcel
|
Looks good so far for Squeak 5.3 on a Surface Pro 6 (Windows 10). Only that AllocationTest >> #testOutOfMemorySignal is still an issue. But that's independent from this VM version. Best, Marcel
|
In reply to this post by marcel.taeumel
> On 2020-04-30, at 12:59 AM, Marcel Taeumel <[hidden email]> wrote: > > Hi all! > > I will now test 202004292351 as a release candidate for a new VM release to be also used in Squeak 5.3 to fix ARM support. It looks 'mostly OK' to me. a) it doesn't segfault on startup; always a bonus. b) tinyBenchmarks are typical, so likely no broken cog mechanism c) running the full test suite - 4726 run, 38 expected failures, 5 failures, 17 errors. The 6 failures include - TextAnchorTest>>#testResizeAnchoredMorph (anchoredMorph is shadowed and the self assert: priorExtent y + 15 equals: textMorph height. fails because priorExtent is 84 and textMorph height is 84 - so adding 15 isn't a happy maker - HashedCollectionTest>>#testSizeFor fails because the very first value tested is 0 and we end up noticing the 0.0 / 5 is not > than 0.75. - IntervalTest>>#testIntervalOfFloatLast fails because of floating point insanity. Will we ever be able to trust them? - IntervalTest>>#testIntervalOfFloatReversed & #testSurprisingFuzzyInclusionBehavior same basic issue The errors - - AllocationTest>>#testOutOfMemorySignal fails to set the free space limit of 1.5 GB on a 4GB Pi - 3 Decompiler tests fail because somebody thought using _ for := is still acceptable a million years after we changed that. - DecompilerTests>>#testDecompilerInClassesVAtoVM fails because the first assert has conniptions over the tempVector having voted for trump - 12 SqueakSSLTests fail because they know it would be annoying. Only the #testFaceBookAPI passes, which is also to be annoying. Only the SSL failures seem like a potential problem here - does it indicate the plugin is borked? tim -- tim Rowledge; [hidden email]; http://www.rowledge.org/tim "How many Trinoc does it take to change a lightbulb?” "Why do you want to know about our maintenance schedules? Are you planning to attack us in the dark?" |
> On 2020-05-06, at 5:55 PM, tim Rowledge <[hidden email]> wrote: > > > Only the SSL failures seem like a potential problem here - does it indicate the plugin is borked? D'oh - or is the example cert file in SqueakSSL out of date etc? tim -- tim Rowledge; [hidden email]; http://www.rowledge.org/tim The world will end in 5 minutes. Please log out. |
> On 2020-05-06, at 6:02 PM, tim Rowledge <[hidden email]> wrote: > > > >> On 2020-05-06, at 5:55 PM, tim Rowledge <[hidden email]> wrote: >> >> >> Only the SSL failures seem like a potential problem here - does it indicate the plugin is borked? > > D'oh - or is the example cert file in SqueakSSL out of date etc? Ah, maybe... $ openssl x509 -in /Users/tim/Desktop/SqueakSSLCert.pem -----BEGIN CERTIFICATE----- MIICxTCCAi6gAwIBAgIJAN/0HUpkM5dvMA0GCSqGSIb3DQEBBQUAMEwxCzAJBgNV BAYTAkdCMRIwEAYDVQQIEwlCZXJrc2hpcmUxEDAOBgNVBAcTB05ld2J1cnkxFzAV BgNVBAoTDk15IENvbXBhbnkgTHRkMB4XDTExMDYwNjE0MzcyMFoXDTEyMDYwNTE0 MzcyMFowTDELMAkGA1UEBhMCR0IxEjAQBgNVBAgTCUJlcmtzaGlyZTEQMA4GA1UE BxMHTmV3YnVyeTEXMBUGA1UEChMOTXkgQ29tcGFueSBMdGQwgZ8wDQYJKoZIhvcN AQEBBQADgY0AMIGJAoGBAOcK/+DEMJvbKrXmqQ3Bi10w4d9brT0KTvB/CNWDNI2D 4fD7VHj6StaFhGxahdlRzL3E8L1aGcUIWKNydE5xanu8HJW6QWRU9iDOTU4EVPjz hkIsGZ7TwaotLNmuOC7tzVi7kz0xlB1ko5sG9nMMWye8Vxx8zsbmZf8WABNqxhot AgMBAAGjga4wgaswHQYDVR0OBBYEFGFwXmx2B6FB25yKMBm6g884lB2xMHwGA1Ud IwR1MHOAFGFwXmx2B6FB25yKMBm6g884lB2xoVCkTjBMMQswCQYDVQQGEwJHQjES MBAGA1UECBMJQmVya3NoaXJlMRAwDgYDVQQHEwdOZXdidXJ5MRcwFQYDVQQKEw5N eSBDb21wYW55IEx0ZIIJAN/0HUpkM5dvMAwGA1UdEwQFMAMBAf8wDQYJKoZIhvcN AQEFBQADgYEAbjMF7YzNQGovKD4NRjsnnKzQnUCTw6UquY2Oz/5SeLcPfLm8DudF qppAjJjNpAgYC0yWoWcIxatYF/AsgGc2WL3hzI8oK7by6STfVi5RfLA6jS7lIDOv 4BUVsWZKADbEPsfiwed9b9MLLx8gpLLBrrr2rZpSyeDu4v16haV6wg8= -----END CERTIFICATE----- Diziet:~ tim$ openssl x509 -in /Users/tim/Desktop/SqueakSSLCert.pem -text Certificate: Data: Version: 3 (0x2) Serial Number: 16137555570121217903 (0xdff41d4a6433976f) Signature Algorithm: sha1WithRSAEncryption Issuer: C=GB, ST=Berkshire, L=Newbury, O=My Company Ltd Validity Not Before: Jun 6 14:37:20 2011 GMT Not After : Jun 5 14:37:20 2012 GMT Subject: C=GB, ST=Berkshire, L=Newbury, O=My Company Ltd Tell me if I'm losing track of dates in the current crisis but I think Jun 2012 might have passed. tim -- tim Rowledge; [hidden email]; http://www.rowledge.org/tim Strange OpCodes: IKI: Ignore Keyboard Input |
> On 07.05.2020, at 03:11, tim Rowledge <[hidden email]> wrote: > > > >> On 2020-05-06, at 6:02 PM, tim Rowledge <[hidden email]> wrote: >> >> >> >>> On 2020-05-06, at 5:55 PM, tim Rowledge <[hidden email]> wrote: >>> >>> >>> Only the SSL failures seem like a potential problem here - does it indicate the plugin is borked? >> >> D'oh - or is the example cert file in SqueakSSL out of date etc? > > Ah, maybe... > > $ openssl x509 -in /Users/tim/Desktop/SqueakSSLCert.pem > -----BEGIN CERTIFICATE----- > MIICxTCCAi6gAwIBAgIJAN/0HUpkM5dvMA0GCSqGSIb3DQEBBQUAMEwxCzAJBgNV > BAYTAkdCMRIwEAYDVQQIEwlCZXJrc2hpcmUxEDAOBgNVBAcTB05ld2J1cnkxFzAV > BgNVBAoTDk15IENvbXBhbnkgTHRkMB4XDTExMDYwNjE0MzcyMFoXDTEyMDYwNTE0 > MzcyMFowTDELMAkGA1UEBhMCR0IxEjAQBgNVBAgTCUJlcmtzaGlyZTEQMA4GA1UE > BxMHTmV3YnVyeTEXMBUGA1UEChMOTXkgQ29tcGFueSBMdGQwgZ8wDQYJKoZIhvcN > AQEBBQADgY0AMIGJAoGBAOcK/+DEMJvbKrXmqQ3Bi10w4d9brT0KTvB/CNWDNI2D > 4fD7VHj6StaFhGxahdlRzL3E8L1aGcUIWKNydE5xanu8HJW6QWRU9iDOTU4EVPjz > hkIsGZ7TwaotLNmuOC7tzVi7kz0xlB1ko5sG9nMMWye8Vxx8zsbmZf8WABNqxhot > AgMBAAGjga4wgaswHQYDVR0OBBYEFGFwXmx2B6FB25yKMBm6g884lB2xMHwGA1Ud > IwR1MHOAFGFwXmx2B6FB25yKMBm6g884lB2xoVCkTjBMMQswCQYDVQQGEwJHQjES > MBAGA1UECBMJQmVya3NoaXJlMRAwDgYDVQQHEwdOZXdidXJ5MRcwFQYDVQQKEw5N > eSBDb21wYW55IEx0ZIIJAN/0HUpkM5dvMAwGA1UdEwQFMAMBAf8wDQYJKoZIhvcN > AQEFBQADgYEAbjMF7YzNQGovKD4NRjsnnKzQnUCTw6UquY2Oz/5SeLcPfLm8DudF > qppAjJjNpAgYC0yWoWcIxatYF/AsgGc2WL3hzI8oK7by6STfVi5RfLA6jS7lIDOv > 4BUVsWZKADbEPsfiwed9b9MLLx8gpLLBrrr2rZpSyeDu4v16haV6wg8= > -----END CERTIFICATE----- > Diziet:~ tim$ openssl x509 -in /Users/tim/Desktop/SqueakSSLCert.pem -text > Certificate: > Data: > Version: 3 (0x2) > Serial Number: 16137555570121217903 (0xdff41d4a6433976f) > Signature Algorithm: sha1WithRSAEncryption > Issuer: C=GB, ST=Berkshire, L=Newbury, O=My Company Ltd > Validity > Not Before: Jun 6 14:37:20 2011 GMT > Not After : Jun 5 14:37:20 2012 GMT > Subject: C=GB, ST=Berkshire, L=Newbury, O=My Company Ltd > > Tell me if I'm losing track of dates in the current crisis but I think Jun 2012 might have passed. I'd be rather impressed if the cert check suddenly passed on openssl :D ;) -t |
Hey Tim! Any updates on VM https://bintray.com/opensmalltalk/vm/cog/202004292351 ? Would it work for 5.3 on ARM? Best, Marcel
|
> On 2020-05-15, at 1:13 AM, Marcel Taeumel <[hidden email]> wrote: > > Hey Tim! > > Any updates on VM https://bintray.com/opensmalltalk/vm/cog/202004292351 ? Would it work for 5.3 on ARM? Well, it works pretty well. I was doing all those tests last week/end though and there is the potential issue of the socket tests that fail (despite the fact that evidently sockets mostly work since I can do MC stuff!) etc. tim -- tim Rowledge; [hidden email]; http://www.rowledge.org/tim Debugger: A tool that substitutes afterthought for forethought. |
Free forum by Nabble | Edit this page |