Vm-dev April 2018

vm-dev@lists.squeakfoundation.org

43 participants
235 discussions

VM Maker: ImageFormat-dtl.30.mcz
by commits＠source.squeak.org 14 Apr '18

14 Apr '18

David T. Lewis uploaded a new version of ImageFormat to project VM Maker: http://source.squeak.org/VMMaker/ImageFormat-dtl.30.mcz ==================== Summary ==================== Name: ImageFormat-dtl.30 Author: dtl Time: 13 April 2018, 6:19:53.496 pm UUID: a56c3b22-9d7a-4db7-aaf7-2240dfb4f561 Ancestors: ImageFormat-dtl.29 Fix declaration of main() in ckformat.c =============== Diff against ImageFormat-dtl.29 =============== Item was changed: ----- Method: ImageFormat class>>generateCkFormatProgram:on: (in category 'ckformat') ----- generateCkFormatProgram: programName on: stream "Generate source code for an image format version reader. The program is intended for testing image file format from a unix shell script such that the shell script can decide what VM to run based on image requirements." | formatNumber | stream nextPutAll: '/* ', programName, ': Print the image format number on standard output */'; cr; nextPutAll: '/* for use in a shell script to test image format requirements. */'; cr; nextPutAll: '/* A non-zero return status code indicates failure. */'; cr; cr; nextPutAll: '/* Usage: ', programName, ' imageFileName */'; cr; cr; nextPutAll: '/* --- DO NOT EDIT THIS FILE --- */'; cr; nextPutAll: '/* --- Automatically generated from class ', self name, ' ', DateAndTime now asString, '--- */'; cr; nextPutAll: '/* --- Source code is in package ImageFormat in the VMMaker repository --- */'; cr; nextPutAll: '/* --- DO NOT EDIT THIS FILE --- */'; cr; cr; nextPutAll: '#include <stdio.h>'; cr; nextPutAll: '#include <stdlib.h>'; cr; nextPutAll: '#include <string.h>'; cr; cr; + nextPutAll: 'int main(int argc, char **argv) {'; cr; - nextPutAll: 'main(int argc, char **argv) {'; cr; tab; nextPutAll: 'FILE *f;'; cr; tab; nextPutAll: 'unsigned char buf[8];'; cr; tab; nextPutAll: 'int formatNumber;'; cr; tab; nextPutAll: 'unsigned char c;'; cr; tab; nextPutAll: 'int match;'; cr; tab; nextPutAll: 'if (argc !!= 2) {'; cr; tab; tab; nextPutAll: 'printf("usage: ', programName, ' imageFileName\n");'; cr; tab; tab; nextPutAll: 'exit(1);'; cr; tab; nextPutAll: '}'; cr; tab; nextPutAll: 'f = fopen(argv[1], "r");'; cr; tab; nextPutAll: 'if (f == NULL) {'; cr; tab; tab; nextPutAll: 'perror(argv[1]);'; cr; tab; tab; nextPutAll: 'exit(2);'; cr; tab; nextPutAll: '}'; cr. { 0. 512 } do: [:offset | stream tab; nextPutAll: 'if(fseek(f, '; nextPutAll: offset asString; nextPutAll: 'L, SEEK_SET) !!= 0) {';cr; tab; tab; nextPutAll: 'fprintf(stderr, "cannot go to pos %d in %s\n", '; nextPutAll: offset asString; nextPutAll: ', argv[1]);'; cr; tab; tab; nextPutAll: 'exit(3);'; cr; tab; nextPutAll: '}'; cr; tab; nextPutAll: 'if (fread(buf, 1, 8, f) < 8) {'; cr; tab; tab; nextPutAll: 'fprintf(stderr, "cannot read %s\n", argv[1]);'; cr; tab; tab; nextPutAll: 'exit(3);'; cr; tab; nextPutAll: '}'; cr. self versionNumberByteArrays withIndexDo: [ :v :tag | | b | formatNumber := (self fromBytes: v) asInteger. b := 'b_', formatNumber asString, '_', tag asString. stream tab; nextPutAll: '{'; cr; tab; nextPutAll: 'unsigned char ', b, '[', v size asString, ']= { '. v inject: true into: [:first : elem | first ifFalse: [stream nextPutAll: ', ']. stream nextPutAll: elem asString. false]. stream nextPutAll: '};'; cr; tab; nextPutAll: 'if (memcmp(buf, ', b, ', ', v size asString, ') == 0) {'; cr; tab; tab; nextPutAll: 'printf("%d\n", ', formatNumber, ');'; cr; tab; tab; nextPutAll: 'exit(0);'; cr; tab; nextPutAll: '}'; cr; tab; nextPutAll: '}'; cr]]. stream tab; nextPutAll: 'printf("0\n"); /* print an invalid format number */';cr; tab; nextPutAll: 'exit (-1); /* not found, exit with error code */'; cr; nextPutAll: '}'; cr !

1 0

[OpenSmalltalk/opensmalltalk-vm] Correct typos and add documentation about ./mvm -f (#246)
by CyrilFerlicot 14 Apr '18

14 Apr '18

I heard that in windows and OSX it is possible to only compile the production vm with `./mvm -f`. Since it was not written in the HozToBuild files, this PR add the documentation. Please correct me if I'm wrong! You can view, comment on, or merge this pull request online at: https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/246 -- Commit Summary -- * Correct typos and add documentation about ./mvm -f -- File Changes -- M build.linux32ARMv6/HowToBuild (5) M build.linux32ARMv7/HowToBuild (7) M build.linux32x86/HowToBuild (7) M build.linux64x64/HowToBuild (5) M build.macos32x86/HowToBuild (4) M build.macos64x64/HowToBuild (4) M build.win32x86/HowToBuild (4) M build.win64x64/HowToBuild (4) -- Patch Links -- https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/246.patch https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/246.diff -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/246

2 1

[OpenSmalltalk/opensmalltalk-vm] 067e96: Correct typos and add documentation about ./mvm -f
by GitHub 14 Apr '18

14 Apr '18

Branch: refs/heads/Cog Home: https://github.com/OpenSmalltalk/opensmalltalk-vm Commit: 067e96dc7be4d342bd68c2dec683333c946a18e7 https://github.com/OpenSmalltalk/opensmalltalk-vm/commit/067e96dc7be4d342bd… Author: CyrilFerlicot <cyril(a)ferlicot.me> Date: 2018-04-10 (Tue, 10 Apr 2018) Changed paths: M build.linux32ARMv6/HowToBuild M build.linux32ARMv7/HowToBuild M build.linux32x86/HowToBuild M build.linux64x64/HowToBuild M build.macos32x86/HowToBuild M build.macos64x64/HowToBuild M build.win32x86/HowToBuild M build.win64x64/HowToBuild Log Message: ----------- Correct typos and add documentation about ./mvm -f Commit: 83397577283b3da45a698dbd3e7925afb8d76d1d https://github.com/OpenSmalltalk/opensmalltalk-vm/commit/83397577283b3da45a… Author: Eliot Miranda <eliot.miranda(a)gmail.com> Date: 2018-04-13 (Fri, 13 Apr 2018) Changed paths: M build.linux32ARMv6/HowToBuild M build.linux32ARMv7/HowToBuild M build.linux32x86/HowToBuild M build.linux64x64/HowToBuild M build.macos32x86/HowToBuild M build.macos64x64/HowToBuild M build.win32x86/HowToBuild M build.win64x64/HowToBuild Log Message: ----------- Merge pull request #246 from jecisc/cf_AddDocAboutMVMF [ci skip] Correct typos and add documentation about ./mvm -f Compare: https://github.com/OpenSmalltalk/opensmalltalk-vm/compare/233d67c88085...83…

1 0

Build completed: opensmalltalk-vm 1.0.1258
by AppVeyor 13 Apr '18

13 Apr '18

1 0

Build failed: opensmalltalk-vm 1.0.1257
by AppVeyor 13 Apr '18

13 Apr '18

3 2

[OpenSmalltalk/opensmalltalk-vm] [ci skip] Remove old files not useful anymore (#247)
by CyrilFerlicot 13 Apr '18

13 Apr '18

I think that the old README and the empty CHANGES files are not useful anymore (the old README will still be in the history if needed). This PR remove them. If you think I'm wrong just close this PR, it's fine with me. You can view, comment on, or merge this pull request online at: https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/247 -- Commit Summary -- * Remove old files not useful anymore. -- File Changes -- D CHANGES (1) D README.old (251) -- Patch Links -- https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/247.patch https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/247.diff -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/247

2 1

[OpenSmalltalk/opensmalltalk-vm] 0e6b0d: Remove old files not useful anymore.
by GitHub 13 Apr '18

13 Apr '18

Branch: refs/heads/Cog Home: https://github.com/OpenSmalltalk/opensmalltalk-vm Commit: 0e6b0db6b7067b83973326ee75e3c54e59a547f1 https://github.com/OpenSmalltalk/opensmalltalk-vm/commit/0e6b0db6b7067b8397… Author: CyrilFerlicot <cyril(a)ferlicot.me> Date: 2018-04-12 (Thu, 12 Apr 2018) Changed paths: R CHANGES R README.old Log Message: ----------- Remove old files not useful anymore. Commit: 233d67c88085665e32c5ee9b0b047be4745f5778 https://github.com/OpenSmalltalk/opensmalltalk-vm/commit/233d67c88085665e32… Author: Eliot Miranda <eliot.miranda(a)gmail.com> Date: 2018-04-13 (Fri, 13 Apr 2018) Changed paths: R CHANGES R README.old Log Message: ----------- Merge pull request #247 from jecisc/cf_removeOldFiles [ci skip] Remove old files not useful anymore Compare: https://github.com/OpenSmalltalk/opensmalltalk-vm/compare/07c6dc319fe6...23…

1 0

Re: [Vm-dev] [squeak-dev] Usability of Squeak FFI for anything serious...
by Eliot Miranda 13 Apr '18

13 Apr '18

On Fri, Apr 13, 2018 at 10:59 AM, Nicolas Cellier < nicolas.cellier.aka.nice(a)gmail.com> wrote: > > > 2018-04-13 17:08 GMT+02:00 Eliot Miranda <eliot.miranda(a)gmail.com>: > >> Hi Nicolas, >> >> >> On Apr 13, 2018, at 7:01 AM, Nicolas Cellier < >> nicolas.cellier.aka.nice(a)gmail.com> wrote: >> >> So I started to improve the Squeak FFI: >> -1) I corrected pointer arithmetic on 64 bits >> http://source.squeak.org/FFI/FFI-Kernel-nice.48.diff >> -2) I prepared the possibility of having automated layout spec updates >> http://source.squeak.org/FFI/FFI-Kernel-nice.49.diff >> >> Note that the FFI plugin by itself did not change. >> The next steps should be to provide support for native platform alignment >> of fields and unions. >> I'll focus on these when i can. >> >> >> I shall join you as soon as I am able. Right now I have a pressing task, >> but within a few weeks I should be able to help. >> >> > Hi Eliot, > thanks. > I think that I can manage the easiest image side issues, but as soon as a > feature will require an evolution of the plugin, your review is mandatory, > as well as coordination with Pharo team, Backward compatibility counts and > Esteban spent enough time on UFFI, so this will mean either unifying our > forces or forking a plugin! > Sounds good. A fork is to be avoided at all costs. I don't see any pressure for a fork though because the plugin is essentially defined by the platform's ABI and Andreas' design for the type specification language is sufficiently general. Am I missing something? (Esteban are you reading?) 2018-04-12 23:27 GMT+02:00 Denis Kudriashov <dionisiydk(a)gmail.com>: >> >>> Hi >>> >>> There is project TalkFFI <https://github.com/estebanlm/TalkFFI> from >>> Ciprian Teodorov. >>> >>> 2018-04-12 22:50 GMT+02:00 Bert Freudenberg <bert(a)freudenbergs.de>: >>> >>>> On 12 April 2018 at 22:34, Nicolas Cellier < >>>> nicolas.cellier.aka.nice(a)gmail.com> wrote: >>>> >>>>> >>>>> There are at least two problems: >>>>> - documentation (lack of) >>>>> - limitations (unions, pointer on pointer on ...) >>>>> - automation (I said at least two, not at most) >>>>> >>>>> For the first problem, I opened the SO issues. Not ideal, but it's a >>>>> start. >>>>> For the second, I'll see if I can do something... >>>>> For the third, I did import some .h header with VW DLLCC, and I'm in >>>>> the process of translating to other dialects. >>>>> It's easier because Smalltalk syntax is order of magnitudes smaller >>>>> than C syntax. >>>>> >>>> >>>> I always thought it should be fairly straightforward to make a FFI >>>> bindings generator using SWIG (http://www.swig.org/). >>>> >>>> SWIG parses C headers and outputs XML. Starting from that XML should be >>>> way easier than trying to parse C ourselves. >>>> >>>> - Bert - >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>> >>> >>> >>> >> >> >> >> >> > > > > -- _,,,^..^,,,_ best, Eliot

2 2

VM Maker: ImageFormat-dtl.29.mcz
by commits＠source.squeak.org 13 Apr '18

13 Apr '18

David T. Lewis uploaded a new version of ImageFormat to project VM Maker: http://source.squeak.org/VMMaker/ImageFormat-dtl.29.mcz ==================== Summary ==================== Name: ImageFormat-dtl.29 Author: dtl Time: 11 April 2018, 8:54:16.07 am UUID: ea0c2ff3-c413-4917-a6fb-8177e5a2ebec Ancestors: ImageFormat-dtl.28 Fix by K K Subbu: Use memcmp instead of strncmp in ckformat to compare byte arrays. =============== Diff against ImageFormat-dtl.28 =============== Item was changed: ----- Method: ImageFormat class>>generateCkFormatProgram:on: (in category 'ckformat') ----- generateCkFormatProgram: programName on: stream "Generate source code for an image format version reader. The program is intended for testing image file format from a unix shell script such that the shell script can decide what VM to run based on image requirements." | formatNumber | stream nextPutAll: '/* ', programName, ': Print the image format number on standard output */'; cr; nextPutAll: '/* for use in a shell script to test image format requirements. */'; cr; nextPutAll: '/* A non-zero return status code indicates failure. */'; cr; cr; nextPutAll: '/* Usage: ', programName, ' imageFileName */'; cr; cr; nextPutAll: '/* --- DO NOT EDIT THIS FILE --- */'; cr; nextPutAll: '/* --- Automatically generated from class ', self name, ' ', DateAndTime now asString, '--- */'; cr; nextPutAll: '/* --- Source code is in package ImageFormat in the VMMaker repository --- */'; cr; nextPutAll: '/* --- DO NOT EDIT THIS FILE --- */'; cr; cr; nextPutAll: '#include <stdio.h>'; cr; nextPutAll: '#include <stdlib.h>'; cr; nextPutAll: '#include <string.h>'; cr; cr; nextPutAll: 'main(int argc, char **argv) {'; cr; tab; nextPutAll: 'FILE *f;'; cr; tab; nextPutAll: 'unsigned char buf[8];'; cr; tab; nextPutAll: 'int formatNumber;'; cr; tab; nextPutAll: 'unsigned char c;'; cr; tab; nextPutAll: 'int match;'; cr; tab; nextPutAll: 'if (argc !!= 2) {'; cr; tab; tab; nextPutAll: 'printf("usage: ', programName, ' imageFileName\n");'; cr; tab; tab; nextPutAll: 'exit(1);'; cr; tab; nextPutAll: '}'; cr; tab; nextPutAll: 'f = fopen(argv[1], "r");'; cr; tab; nextPutAll: 'if (f == NULL) {'; cr; tab; tab; nextPutAll: 'perror(argv[1]);'; cr; tab; tab; nextPutAll: 'exit(2);'; cr; tab; nextPutAll: '}'; cr. { 0. 512 } do: [:offset | stream tab; nextPutAll: 'if(fseek(f, '; nextPutAll: offset asString; nextPutAll: 'L, SEEK_SET) !!= 0) {';cr; tab; tab; nextPutAll: 'fprintf(stderr, "cannot go to pos %d in %s\n", '; nextPutAll: offset asString; nextPutAll: ', argv[1]);'; cr; tab; tab; nextPutAll: 'exit(3);'; cr; tab; nextPutAll: '}'; cr; tab; nextPutAll: 'if (fread(buf, 1, 8, f) < 8) {'; cr; tab; tab; nextPutAll: 'fprintf(stderr, "cannot read %s\n", argv[1]);'; cr; tab; tab; nextPutAll: 'exit(3);'; cr; tab; nextPutAll: '}'; cr. self versionNumberByteArrays withIndexDo: [ :v :tag | | b | formatNumber := (self fromBytes: v) asInteger. b := 'b_', formatNumber asString, '_', tag asString. stream tab; nextPutAll: '{'; cr; tab; nextPutAll: 'unsigned char ', b, '[', v size asString, ']= { '. v inject: true into: [:first : elem | first ifFalse: [stream nextPutAll: ', ']. stream nextPutAll: elem asString. false]. stream nextPutAll: '};'; cr; + tab; nextPutAll: 'if (memcmp(buf, ', b, ', ', v size asString, ') == 0) {'; cr; - tab; nextPutAll: 'if (strncmp(buf, ', b, ', ', v size asString, ') == 0) {'; cr; tab; tab; nextPutAll: 'printf("%d\n", ', formatNumber, ');'; cr; tab; tab; nextPutAll: 'exit(0);'; cr; tab; nextPutAll: '}'; cr; tab; nextPutAll: '}'; cr]]. stream tab; nextPutAll: 'printf("0\n"); /* print an invalid format number */';cr; tab; nextPutAll: 'exit (-1); /* not found, exit with error code */'; cr; nextPutAll: '}'; cr !

6 9

Re: [Vm-dev] [squeak-dev] Apple starting to alert users that it will end 32-bit app support on the Mac
by Eliot Miranda 13 Apr '18

13 Apr '18

Hi Bert, On Thu, Apr 12, 2018 at 1:34 PM, Bert Freudenberg <bert(a)freudenbergs.de> wrote: > > > On 12 April 2018 at 16:31, Tobias Pape <Das.Linux(a)gmx.de> wrote: > >> Hi >> >> On 12.04.2018, at 16:05, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: >> >> Hi Bert, >> >> >> On Apr 12, 2018, at 6:03 AM, Bert Freudenberg <bert(a)freudenbergs.de> >> wrote: >> >> If that's indeed the case we need to make a 64 bit VM for 32 bit images. >> I think this should be just a matter of picking the right compiler options. >> >> >> How so? AFAIA it is not. It means, for example, changing every memory >> access for an instance variable from 64 to 32 bits. It is non-trivial. >> >> >> But wasn't that done once already? >> >> I see Squeak 5.7.4.1 (John Macintosh did it I think). >> Wich advertises itself as >> >> and worked very well. Not saying every bits are there for the present >> (spur etc) >> but at least, we have been there already at least once… >> > > Yep. Its just the 32 bit VM compiled on a 64 bit host. This worked > without big problems on the interpreter. I don't know what additional > constraints are imposed by Cog / Spur, but I thought at least for intel, > the 32 bit instruction set was a strict subset of x64, so there should be > no big problems. > The main problem is in arranging that the heap is allocated in the 32-bit addressable part of the address space. It's also effectively another VM to support, with its won bizarre configuration of FFI (64-bit) for a 32-bit client. That could be expensive. The thing that the above 64-bit system did that made it quick to port but under-performant was to keep oops exactly the same as in 32-bits, but simply make them occupy 64-bits. SmallIntegers had the same range as in 32-bits. And I'm guessing that this predated Andreas' FFI, so it could avoid addressing the FFI issue. We can't. If we wanted full support we would have to provide a way of loading 32-bit dlls and calling them via the FFI through the 32-bit calling convention. That's not trivial. That's why for me by far the simplest thing is to convert. _,,,^..^,,,_ best, Eliot

3 2

← Newer
1
...
7
8
9
10
11
12
13
...
24
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

Vm-dev April 2018