Skip to content
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

fix(hipblas): disable avx flags when accellerated bins are used #4167

Merged
merged 1 commit into from
Nov 17, 2024

Conversation

mudler
Copy link
Owner

@mudler mudler commented Nov 16, 2024

Description

Seems the hipblas binary still have AVX and other CPU flags that might be problematic on old HW. As hipblas is reserved in cases of running inference on GPU, CPU optimizations aren't needed and actually just causes sigsev when running binaries.

Notes for Reviewers

See: #3367 (comment)

Signed commits

  • Yes, I signed my commits.

@mudler mudler changed the title chore(hipblas): disable avx flags when accellerated bins are used fix(hipblas): disable avx flags when accellerated bins are used Nov 16, 2024
@mudler mudler added the bug Something isn't working label Nov 16, 2024
Copy link

netlify bot commented Nov 16, 2024

Deploy Preview for localai ready!

Name Link
🔨 Latest commit 8ddd01c
🔍 Latest deploy log https://app.netlify.com/sites/localai/deploys/6738a483b31ac600081e586c
😎 Deploy Preview https://deploy-preview-4167--localai.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@chris-hatton
Copy link

Thanks so much for this @mudler - looking forward to confirming the fix as soon as possible.

@mudler mudler merged commit e898e0b into master Nov 17, 2024
32 of 33 checks passed
@mudler mudler deleted the fix/hipblas_avx branch November 17, 2024 09:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants