You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There's apparently an assumption that pmuv3 is always unconditionally available, which is demonstrably not true; this originally came up as an issue for the Apple M1 family of platforms, which have their own non-standard PMU instead, but even in the Arm ARM it states that FEAT_PMUv3 is optional. This problem occurs not just for aarch64-unknown-none-softfloat but for all aarch64 targets in current (2022-03-24) nightly.
(This is a continuation from the discussion at the end of #95122.)
I tried this shell invocation:
I expected to see this happen:
No meaningful
target_feature
s should be printed.Instead, this happened:
There's apparently an assumption that
pmuv3
is always unconditionally available, which is demonstrably not true; this originally came up as an issue for the Apple M1 family of platforms, which have their own non-standard PMU instead, but even in the Arm ARM it states that FEAT_PMUv3 is optional. This problem occurs not just foraarch64-unknown-none-softfloat
but for allaarch64
targets in current (2022-03-24) nightly.Meta
rustc --version --verbose
:The text was updated successfully, but these errors were encountered: