-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create a build of Bun that doesn’t need AVX2 instructions #67
Comments
What next? |
For the time being, I've made a script to simplify and automate SDE's installation based on @renhiyama 's solution, lmk if there's anything to fix.
EDIT: Updated script, this one is up to date. |
This comment was marked as off-topic.
This comment was marked as off-topic.
Did you restart your shell ? |
This comment was marked as off-topic.
This comment was marked as off-topic.
Reload the terminal, not the OS |
This comment was marked as off-topic.
This comment was marked as off-topic.
|
This comment was marked as off-topic.
This comment was marked as off-topic.
@guest271314 restart your terminal and then try again, should be working |
also you should be running |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
and thats not gonna work for you... |
You're still using the original bun executable. The script does not patch bun, but uses SDE as a middleman to handle the avx2 set. You have to run |
Hi. Rust can check CPU features and whether the OS supports them. |
This comment was marked as off-topic.
This comment was marked as off-topic.
AFAIK the issue is that we don't support devices without AVX2 at all yet, not that we can't tell if they support that instruction set or not. |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
We usually check whether the environment has AVX2 and run fallback functions instead of SIMD functions. I think it's the right way to support old devices.
|
Because it's a pretty new bug, and should not be documented because it should not be a problem in the first place. Can you send the output of
If not, the installation is faulty somehow, which would be either an issue with |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
I imagine you read the top of the README carefully and noticed this line:
No. At least not officially. That might be the problem. Look up if there is an emulator for AMD CPUs. If so, you can apply the same workaround. I won't be of any help since all my computers are running on Intel CPUs. |
This issue is cause by an instruction set that is not present on older CPUs. I believe that the contributors are all running on modern CPUs, so they didn't run into this issue before the release of v.0.1.0. |
This issue was created for tracking progress |
Done, see latest release *-baseline builds. |
This can be feature detected in the install script
It’s really stupid for people to be unable to use Bun on older computers
The text was updated successfully, but these errors were encountered: