You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the only targets enabled in bootstrap compilation are:
ag32
the 32-bit x86 target
the 64-bit x86 target (x86-64)
It would be nice to also enable the arm64 target (arm8): it could run on arm64 Linux, and it will be needed to support modern Apple mac's in the future (which we intend to do).
At the same time, I think we should focus the bootstrap compilation on running only useful targets, since it takes a long time (and lots of energy). I suspect the 32-bit x86 target is probably not used by anyone, and I know for a fact that very few people have access to ag32 hardware. Most other targets supported by the backend are not run in the bootstrap compilation, so running these two 32-bit targets seems a bit arbitrary.
The text was updated successfully, but these errors were encountered:
The problem with disabling any of these is that they'll stop working at some point and will be very hard to fix. I would support adding more targets though.
Separately I think it's prudent to include at least one 32 bit architecture since that probably exercises a lot of different code than the 64 bit ones.
Currently, the only targets enabled in bootstrap compilation are:
It would be nice to also enable the arm64 target (arm8): it could run on arm64 Linux, and it will be needed to support modern Apple mac's in the future (which we intend to do).
At the same time, I think we should focus the bootstrap compilation on running only useful targets, since it takes a long time (and lots of energy). I suspect the 32-bit x86 target is probably not used by anyone, and I know for a fact that very few people have access to ag32 hardware. Most other targets supported by the backend are not run in the bootstrap compilation, so running these two 32-bit targets seems a bit arbitrary.
The text was updated successfully, but these errors were encountered: