-
-
Notifications
You must be signed in to change notification settings - Fork 12.5k
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
hashcat: fix metal library detection, skip OpenCL on virtualized ARM #183847
Conversation
Do you not need the patch from #181921? |
Maybe needed. Locally, I can install existing Monterey bottle and it finds Metal but may have some issues with recent builds ❯ hashcat_bin --benchmark -m 0 -D 1,2 -w 2 --backend-ignore-opencl
hashcat (v6.2.6) starting in benchmark mode
METAL API (Metal 343.21)
========================
...
-------------------
* Hash-Mode 0 (MD5)
-------------------
Speed.#1.........: 1519.7 MH/s (9.93ms) @ Accel:512 Loops:128 Thr:32 Vec:1 Could be that There are still remnants of macro usage in Xcode.app though none in CLT: ❯ rg __METAL_MACOS__ /Applications/Xcode.app/Contents/Developer/**/macos
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/metal/macos/lib/clang/32023.155/include/metal/metal_stdlib
39:#if defined(__METAL_MACOS__) && !defined(__METAL__)
67:#endif // __METAL_MACOS__
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/metal/macos/lib/clang/32023.155/include/metal/metal_config
598:#ifdef __METAL_MACOS__
1170:#endif // __METAL_MACOS__ |
Still can't find any devices. Locally, I can confirm:
I think we have Metal on CI given other formulae like: homebrew-core/Formula/v/vulkan-profiles.rb Lines 70 to 71 in a9ae5dc
May need to see what code path to reach Metal detection is and what version of Metal is on runners. |
Well it's not printing
It was a Metal 3.0 change where macOS and iOS paths were combined to a unified one. I think |
Might just have to check failure or Not sure if |
Co-authored-by: Michael Cho <[email protected]>
🤖 An automated task has requested bottles to be published to this PR. |
HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>
, where<formula>
is the name of the formula you're submitting?brew test <formula>
, where<formula>
is the name of the formula you're submitting?brew audit --strict <formula>
(after doingHOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>
)? If this is a new formula, does it passbrew audit --new <formula>
?Superseding #181921 for working on test failure on CI.
EDIT: cherry-picked commit from other PR and thus closes #181921
Needs a new bottle due to attestation