-
Notifications
You must be signed in to change notification settings - Fork 12.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
64-bit OS X support #96
Comments
I'm not sure what the bug here is? Is it just that we don't support 64-bit yet? |
I honestly don't remember; closing. |
keeperofdakeys
pushed a commit
to keeperofdakeys/rust
that referenced
this issue
Dec 12, 2017
SysV shared memory APIs
kazcw
pushed a commit
to kazcw/rust
that referenced
this issue
Oct 23, 2018
* Enable multiple #[assert_instr] attributes Looks like all we needed to do was generate new function names! * Uncomment assertions for `_mm_prefetch`
flip1995
pushed a commit
to flip1995/rust
that referenced
this issue
May 15, 2020
…flip1995 Reversed empty ranges This lint checks range expressions with inverted limits which result in empty ranges. This includes also the ranges used to index slices. The lint reverse_range_loop was covering iteration of reversed ranges in a for loop, which is a subset of what this new lint covers, so it has been removed. I'm not sure if that's the best choice. It would be doable to check in the new lint that we are not in the arguments of a for loop; I went for removing it because the logic was too similar to keep them separated. changelog: Added reversed_empty_ranges lint that checks for ranges where the limits have been inverted, resulting in empty ranges. Removed reverse_range_loop which was covering a subset of the new lint. Closes rust-lang#4192 Closes rust-lang#96
bors
pushed a commit
to rust-lang-ci/rust
that referenced
this issue
Oct 1, 2021
Reduce wasm test suite
djtech-dev
pushed a commit
to djtech-dev/rust
that referenced
this issue
Dec 9, 2021
fix misuse of LLVM API found through inkwell tests
jaisnan
pushed a commit
to jaisnan/rust-dev
that referenced
this issue
Oct 15, 2024
…ed_shl` and `unchecked_shr` (rust-lang#96) Towards : issue rust-lang#59 Parent branch : [c-0011-core-nums-yenyunw-unsafe-ints](https://github.com/rajathkotyal/verify-rust-std/tree/c-0011-core-nums-yenyunw-unsafe-ints ) - Tracking PR rust-lang#91 --------- Co-authored-by: yew005 <yew005@ucsd.edu> Co-authored-by: MWDZ <jinjunfeng721@gmail.com> Co-authored-by: Lanfei Ma <99311320+lanfeima@users.noreply.github.com> Co-authored-by: Yenyun035 <yenyunw@andrew.cmu.edu>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
To determine if OS X is running on a 64-bit box, Homebrew uses:
/usr/sbin/sysctl hw.cpu64bit_capable
We also figure out if we're 10.5 or 10.6 with:
/usr/bin/sw_vers -productVersion
Many of our brews then switch to 64-bit mode if we're on 10.6 (or later) and 64-bit capable, otherwise, on 10.5 or a Core Duo we switch to 32-bit mode.
The text was updated successfully, but these errors were encountered: