[OpenSmalltalk/opensmalltalk-vm] POWER (ppc64le) port. (#493)

 

Unfortunately I'm neither on vm-dev nor on squeak-dev. Anyway, it's here: https://drive.google.com/file/d/1AexePnuVNavu-q0NcMTgg8daQ9jGNr5h/view?usp=sharing -- feel free to download/repost there.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

<script type="application/ld+json">[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/493#issuecomment-621162973", "url": "https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/493#issuecomment-621162973", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]</script>

 

Cool!!
FWIW, I booted up the Unleashed on which we demoed Squeak back in November, to refresh my memory of what I did. In all honesty this is just a quick hack. Here is the patch:
https://github.com/shingarov/opensmalltalk-vm/tree/neuquen-demo
I also included a screenshot of the about-squeak dialog:
https://raw.githubusercontent.com/shingarov/opensmalltalk-vm/neuquen-demo/squeak-riscv64.png

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

<script type="application/ld+json">[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/493#issuecomment-621281000", "url": "https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/493#issuecomment-621281000", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]</script>

 

Cool!!
FWIW, I booted up the Unleashed on which we demoed Squeak back in November, to refresh my memory of what I did. In all honesty this is just a quick hack. Here is the patch:
https://github.com/shingarov/opensmalltalk-vm/tree/neuquen-demo
I also included a screenshot of the about-squeak dialog:
https://raw.githubusercontent.com/shingarov/opensmalltalk-vm/neuquen-demo/squeak-riscv64.png

This is indeed awesome. I've inteded to do that for some years now but never had the opportunity.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

<script type="application/ld+json">[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/493#issuecomment-621347488", "url": "https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/493#issuecomment-621347488", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]</script>

 
For the benefit of vm-dev, here's Squeak running on power64:

 

This is per se a good idea.
Alas, as the other comments succinctly point out, we have limited resources in the community.
This means we have neither hardware nor people nor enough knowledge (yet) to pursue that.

For the hardware, I’m having Windows.
And on Linux, qemu‑user can wrap Linux system calls into native Linux system call without having to ᴊɪᴛ a whole system (should work with anyone).
I even build a rootfs which is able to transparently execute both ᴀᴍᴅ⁶⁴ and Power binaries (much like it’s possible to use mix 32‑bits x86) that way (with native toolchain included).

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

<script type="application/ld+json">[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/493#issuecomment-637855139", "url": "https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/493#issuecomment-637855139", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]</script>

 

Hi Tobias,


> On Apr 29, 2020, at 3:17 AM, Tobias Pape <[hidden email]> wrote:
>
> 
> Yes. this is because of a plugin that is x86-specific
>
>
IA32ABI is *not* platform-specific, it is misnamed. If actually provides the callback machinery for the FFI.


> Please remove the line IA32ABI \
> from build.linux64x64/squeak.stack.spur/plugins.int and start again with ./mvm
>

No, that’s not the right solution at all. The tight thing is yo implrr et next the relevant platform-specific support machinery for callbacks.

> Note that SqueakFFIPrims \ in plugins.ext might also be a candidate…
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub, or unsubscribe.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

<script type="application/ld+json">[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/493#issuecomment-637960869", "url": "https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/493#issuecomment-637960869", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]</script>

 

I'm confused. What is the IA32 about then, if not about x86? https://en.wikipedia.org/wiki/IA-32

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

<script type="application/ld+json">[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/493#issuecomment-637986251", "url": "https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/493#issuecomment-637986251", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]</script>

 

Anyway, to get things to compile I think it's ok to first fogore the FFI machinery and then add necessary callbacks

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

<script type="application/ld+json">[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/493#issuecomment-637986758", "url": "https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/493#issuecomment-637986758", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]</script>