This repository has been archived by the owner on Jan 13, 2025. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 4.5k
Apple M1 compatibility #16346
Merged
Merged
Apple M1 compatibility #16346
Changes from 1 commit
Commits
Show all changes
20 commits
Select commit
Hold shift + click to select a range
fb8d09a
ugh
03f6009
wow, holy fuck it builds lol
10c5e3c
remove unused crap
021d811
remove whitesapce
cdrappi 0ec217b
add MacM1.md readme
cdrappi 405f2c9
homebrew
cdrappi ee9e3ba
move m1 instructions into build readme
cdrappi 8350430
toy around with #cfg(...) options
cdrappi 3693110
add linux only (non mac) config choices which may be bad. we run but …
cdrappi 65ee16b
remove newline in banksclient
cdrappi da4f432
changes
cdrappi 22c3479
oops
cdrappi 4c90d07
giddy up
cdrappi cf48a27
better measure import
cdrappi bca19ea
better comment
cdrappi 1996e5c
new cargo lock
cdrappi ba33540
better place for comment
cdrappi 51e4577
new lockfile
cdrappi c5ffbfe
actually no, blake3 0.3.6 is totally fine
cdrappi 98812e9
cargo fmt
cdrappi File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
oops
- Loading branch information
commit 22c34795cf3f18faf5751076e9d7c6fcc33ee2a2
There are no files selected for viewing
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,3 +1,2 @@ | ||
#![allow(clippy::integer_arithmetic)] | ||
pub mod measure; | ||
pub mod thread_mem_usage; |
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
macos m1 claims to be
target_arch = "x86"
ortarget_arch = "x86_64"
? that seems terribleThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But is that just for the interpreter? There is the mode on m1 to execute x86 code, so it has to report that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
wouldn't this feature check affect the x86 macs which have AVX?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To get this going on an M1, you have to install all of your stuff with Rosetta 2, a tool that allows you to run x86_64 software. This amounts to using a version of rust/cargo etc. that targets
x86_64
instead ofaarch64
. And so to get this running, I had to insert this extremely confusing feature flagWithout Rosetta, rust would target
aarch64
– I tried to do this initially, and gave up after a day as there were several more blockers upstreamThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, got it. Would you mind sneaking in a comment in the code then here about why we're excluding macos. Otherwise somebody with an intel mbp (everybody on the core team) is likely to remove this line later inadvertently
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@sakridge yes it would and is a clear downside of including this feature check. If you could think of a better way to get around this, I'm happy to implement it and be your Mac M1 guinea pig guy
@mvines yes of course! Was planning on this and appreciate the reminder