Vm-dev May 2022

vm-dev@lists.squeakfoundation.org

13 participants
40 discussions

VM Maker Inbox: VMMaker.oscog-dtl.3185.mcz
by commits＠source.squeak.org 02 Jun '22

02 Jun '22

David T. Lewis uploaded a new version of VMMaker to project VM Maker Inbox: http://source.squeak.org/VMMakerInbox/VMMaker.oscog-dtl.3185.mcz ==================== Summary ==================== Name: VMMaker.oscog-dtl.3185 Author: dtl Time: 30 May 2022, 2:36:26.668082 pm UUID: 0e7f07b8-eed6-4362-b223-86c98594ddb9 Ancestors: VMMaker.oscog-mt.3184 Let primitiveImageFormatVersion answer the correct image format number when multiple byte codes are active. =============== Diff against VMMaker.oscog-mt.3184 =============== Item was changed: ----- Method: InterpreterPrimitives>>primitiveImageFormatVersion (in category 'other primitives') ----- primitiveImageFormatVersion "Answer an integer identifying the type of image. The image version number may identify the format of the image (e.g. 32 or 64-bit word size) or specific requirements of the image (e.g. block closure support required). This is a named (not numbered) primitive in the null module (ie the VM)" <export: true> + self pop: 1 thenPush: (self positive32BitIntegerFor: self imageFormatVersionForSnapshot) - self pop: 1 thenPush: (self positive32BitIntegerFor: self imageFormatVersion) !

3 3

Re: [Vm-dev] [squeak-dev] Older VM's won't start the latest beta images
by Marcel Taeumel 30 May '22

30 May '22

Hi Dave -- See https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/638 [https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/638] Should we fix this in the image or in the VM? Best, Marcel Am 30.05.2022 11:48:03 schrieb Marcel Taeumel <marcel.taeumel(a)hpi.de>: Hi Dave -- I wonder why I cannot change the format from 68021 to 68533 via CompiledCode multipleBytecodeSetsActive: true. Smalltalk snapshot: true andQuit: true. Any ideas? At least the System Reporter does not report that format. Is this a VM bug? Best, Marcel Am 29.05.2022 16:04:04 schrieb David T. Lewis <lewis(a)mail.msen.com>: On Sun, May 29, 2022 at 08:06:59AM +0000, Jaromir Matas wrote: > Hi, > I wonder what?s changed that the images starting from Squeak6.0beta-21772-64bit on won?t start with the previous release VM (squeak.cog.spur_win64x64_202003021730) or even with pre-release new VMs (e.g. version 3154). > > I?m on Win10, the process explorer (windows) shortly runs WerFault.exe and than the Squeak process is closed/disappears. > The change is here: http://lists.squeakfoundation.org/pipermail/squeak-dev/2022-May/220660.html The current release candidate image does not have this, but it will be applied as soon as you update that image, and it expected to be part of the final release. The update applies a new image format number to the saved image files (stored in the first 4 bytes of the image file) when multiple bytecode set support is required from the VM. Effectively, the means that the image is using the Sista bytecode set. Older VMs can run the Sista bytecodes but do not yet have the code for recognizing the additional image format number. Dave

1 1

[OpenSmalltalk/opensmalltalk-vm] Primitive 64 (primitiveStringAtPut) does not fail atomically (Issue #636)
by Christoph Thiede 27 May '22

27 May '22

To reproduce, in Squeak, do this: ```smalltalk 'aaa' copy tryPrimitive: 64 withArgs: {2. $b asciiValue}; yourself ``` Expected behavior: The primitive fails, and the string remains `aaa`. This is also what we are used to from primitive 61 (primitiveAtPut). Actual behavior: The primitive fails, but the string slot has been changed to `Character null`. (By the way, TruffleSqueak and SqueakJS show my expected behavior.) Maybe there is some clever reasoning behind it, but a primitive that fails should not have any other side effects from my first impression. Is this a bug? -- Reply to this email directly or view it on GitHub: https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/636 You are receiving this because you are subscribed to this thread. Message ID: <OpenSmalltalk/opensmalltalk-vm/issues/636(a)github.com>

2 1

[OpenSmalltalk/opensmalltalk-vm] 144607: [ci skip] [doc only] Explain FQDN
by Tobias Pape 27 May '22

27 May '22

Branch: refs/heads/Cog Home: https://github.com/OpenSmalltalk/opensmalltalk-vm Commit: 144607df34b6653436907470ae313155e942f883 https://github.com/OpenSmalltalk/opensmalltalk-vm/commit/144607df34b6653436… Author: Tobias Pape <tobias(a)netshed.de> Date: 2022-05-27 (Fri, 27 May 2022) Changed paths: M platforms/unix/plugins/SocketPlugin/sqUnixSocket.c Log Message: ----------- [ci skip] [doc only] Explain FQDN

1 0

[OpenSmalltalk/opensmalltalk-vm] [Unix/Sockets] Fix Resolution of FQDNs >64 chars (PR #635)
by Tobias Pape 26 May '22

26 May '22

We used to use MAXHOSTNAMELEN, but that is 64 on most Linuxen and might be differen w/ or w/o POSIX compliance. We now use the definitions from and implications by DNS itself. Now, we can ``` WebClient httpGet: 'http://theofficialabsolutelongestdomainnameregisteredontheworldwideweb.international/' ``` Fixes #619 You can view, comment on, or merge this pull request online at: https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/635 -- Commit Summary -- * [Unix/Sockets] Fix Resolution of FQDNs >64 chars -- File Changes -- M platforms/unix/plugins/SocketPlugin/sqUnixSocket.c (45) -- Patch Links -- https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/635.patch https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/635.diff -- Reply to this email directly or view it on GitHub: https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/635 You are receiving this because you are subscribed to this thread. Message ID: <OpenSmalltalk/opensmalltalk-vm/pull/635(a)github.com>

2 4

[OpenSmalltalk/opensmalltalk-vm] Cannot resolve domain names longer than 64 characters on linux (Issue #619)
by smalltalking 26 May '22

26 May '22

SocketPlugin uses a buffer of size MAXHOSTNAMELEN + 1 on [unix](https://github.com/OpenSmalltalk/opensmalltalk-vm/blob/6d38f13347be10…. The value of that constant is 64 on linux. A domain name can have up to 255 octets with each label having up to 63 octets. So, 64 is definitely not the right value, nor is MAXHOSTNAMELEN, because the buffer is there to store a domain name, not a host name. -- Reply to this email directly or view it on GitHub: https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/619 You are receiving this because you are subscribed to this thread. Message ID: <OpenSmalltalk/opensmalltalk-vm/issues/619(a)github.com>

3 2

[OpenSmalltalk/opensmalltalk-vm] ebc591: [Unix/Sockets] Fix Resolution of FQDNs >64 chars
by Eliot Miranda 26 May '22

26 May '22

Branch: refs/heads/Cog Home: https://github.com/OpenSmalltalk/opensmalltalk-vm Commit: ebc591451379bd007c2d7eca89d747fc024b76d0 https://github.com/OpenSmalltalk/opensmalltalk-vm/commit/ebc591451379bd007c… Author: Tobias Pape <tobias(a)netshed.de> Date: 2022-05-25 (Wed, 25 May 2022) Changed paths: M platforms/unix/plugins/SocketPlugin/sqUnixSocket.c Log Message: ----------- [Unix/Sockets] Fix Resolution of FQDNs >64 chars We used to use MAXHOSTNAMELEN, but that is 64 on most Linuxen and might be differen w/ or w/o POSIX compliance. We now use the definitions from and implications by DNS itself. Now, we can ``` WebClient httpGet: 'http://theofficialabsolutelongestdomainnameregisteredontheworldwideweb.inte…' ``` Fixes #619 Commit: 572fd1f649f901b50f15f2b46e71400157f3add5 https://github.com/OpenSmalltalk/opensmalltalk-vm/commit/572fd1f649f901b50f… Author: Eliot Miranda <eliot.miranda(a)gmail.com> Date: 2022-05-26 (Thu, 26 May 2022) Changed paths: M platforms/unix/plugins/SocketPlugin/sqUnixSocket.c Log Message: ----------- Merge pull request #635 from OpenSmalltalk/krono/fix-dns-fqdn-len [Unix/Sockets] Fix Resolution of FQDNs >64 chars Compare: https://github.com/OpenSmalltalk/opensmalltalk-vm/compare/61e43f0d3902...57…

1 0

[OpenSmalltalk/opensmalltalk-vm] Ubuntu 22.04. ships with OpenSSL 3 but SqueakSSL plugin depends on OpenSSL 1.1 (Issue #633)
by Patrick R 26 May '22

26 May '22

This breaks SqueakSSL under Ubuntu 22.04. @krono identified part of the problem as: > in <3.0 SSL_get_peer_certificate is a function, in ≥3 it is an "alias" for SSL_get1_peer_certificate > https://www.openssl.org/docs/man3.0/man3/SSL_get_peer_certificate.html -- Reply to this email directly or view it on GitHub: https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/633 You are receiving this because you are subscribed to this thread. Message ID: <OpenSmalltalk/opensmalltalk-vm/issues/633(a)github.com>

2 1

[OpenSmalltalk/opensmalltalk-vm] [SqueakSSL/unix/openssl] Fix for OpenSSL3 (PR #634)
by Tobias Pape 26 May '22

26 May '22

OpenSSL 3 deprecated SSL_get_peer_certificate, made it a macro and an provides SSL_get{0,1}_peer_certificate instead. Why even more complicating that already messed API is beyond me. Not promising ABI stability is well known for OpenSSL but, why the HECK not simply providing an Alias Symbol instead of UNNECESSARILY ripping the symbol out of that innocent object file? Also, we now need a load-time disambiguation of which symbol to use. (if you find a rant in this message, you can keep it) Fixes #633 You can view, comment on, or merge this pull request online at: https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/634 -- Commit Summary -- * [SqueakSSL/unix/openssl] Fix for OpenSSL3 -- File Changes -- M platforms/unix/plugins/SqueakSSL/openssl_overlay.h (9) M platforms/unix/plugins/SqueakSSL/sqUnixOpenSSL.inc (30) -- Patch Links -- https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/634.patch https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/634.diff -- Reply to this email directly or view it on GitHub: https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/634 You are receiving this because you are subscribed to this thread. Message ID: <OpenSmalltalk/opensmalltalk-vm/pull/634(a)github.com>

2 1

[OpenSmalltalk/opensmalltalk-vm] dd435c: [SqueakSSL/unix/openssl] Fix for OpenSSL3
by Eliot Miranda 26 May '22

26 May '22

Branch: refs/heads/Cog Home: https://github.com/OpenSmalltalk/opensmalltalk-vm Commit: dd435c87a9e39d77536969be0c64a364cfd58ea2 https://github.com/OpenSmalltalk/opensmalltalk-vm/commit/dd435c87a9e39d7753… Author: Tobias Pape <tobias(a)netshed.de> Date: 2022-05-25 (Wed, 25 May 2022) Changed paths: M platforms/unix/plugins/SqueakSSL/openssl_overlay.h M platforms/unix/plugins/SqueakSSL/sqUnixOpenSSL.inc Log Message: ----------- [SqueakSSL/unix/openssl] Fix for OpenSSL3 OpenSSL 3 deprecated SSL_get_peer_certificate, made it a macro and an provides SSL_get{0,1}_peer_certificate instead. Why even more complicating that already messed API is beyond me. Not promising ABI stability is well known for OpenSSL but, why the HECK not simply providing an Alias Symbol instead of UNNECESSARILY ripping the symbol out of that innocent object file? Also, we now need a load-time disambiguation of which symbol to use. (if you find a rant in this message, you can keep it) Commit: 61e43f0d39025098d3e8c2ab790dda0f9e88a062 https://github.com/OpenSmalltalk/opensmalltalk-vm/commit/61e43f0d39025098d3… Author: Eliot Miranda <eliot.miranda(a)gmail.com> Date: 2022-05-26 (Thu, 26 May 2022) Changed paths: M platforms/unix/plugins/SqueakSSL/openssl_overlay.h M platforms/unix/plugins/SqueakSSL/sqUnixOpenSSL.inc Log Message: ----------- Merge pull request #634 from OpenSmalltalk/krono/ssl-on-jammy-stuff [SqueakSSL/unix/openssl] Fix for OpenSSL3 Compare: https://github.com/OpenSmalltalk/opensmalltalk-vm/compare/3e3541fec2de...61…

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

Vm-dev May 2022