This repository has been archived by the owner on Mar 24, 2022. It is now read-only.
[WIP] Lucet i686 (32-bit x86) support... ish #508
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
First, why
i686
?i386
has, at best, the x87 FPU for floating point operations. I'm pretty surei686
implies processors recent enough to have MMX/SSE, so our floating point stuff needs fewer changes.The ABI details of lining things up for guest execution are certainly incorrect. The primary issue at this point is our dependencies though,
object
believes it can't targetI686
and Cranelift is missing some legalizations such as 64-bit divides.For object, my suspicion is that just adding a few
I686
matches to patterns where it matches forI386
should be fine. I've yet to test that though :)With object not being able to emit i686 objects this hasn't gotten to a point where anything, yknow, runs. 😁
While this is a relatively unserious PR, this is about the same shape I suspect other architectures for POSIX-y OSes would look, so replace
i686
witharm32
oraarch64
in your imagination!