Open lopopolo opened 2 years ago
'+uwu' is not a recognized feature for this target (ignoring feature)
'+uwu' is not a recognized feature for this target (ignoring feature)
warning: unknown feature specified for `-Ctarget-feature`: `uwu`
|
= note: it is still passed through to the codegen backend
= help: consider filing a feature request
'+uwu' is not a recognized feature for this target (ignoring feature)
'+uwu' is not a recognized feature for this target (ignoring feature)
'+uwu' is not a recognized feature for this target (ignoring feature)
'+uwu' is not a recognized feature for this target (ignoring feature)
'+uwu' is not a recognized feature for this target (ignoring feature)
'+uwu' is not a recognized feature for this target (ignoring feature)
'+uwu' is not a recognized feature for this target (ignoring feature)
'+uwu' is not a recognized feature for this target (ignoring feature)
'+uwu' is not a recognized feature for this target (ignoring feature)
'+uwu' is not a recognized feature for this target (ignoring feature)
'+uwu' is not a recognized feature for this target (ignoring feature)
'+uwu' is not a recognized feature for this target (ignoring feature)
'+uwu' is not a recognized feature for this target (ignoring feature)
'+uwu' is not a recognized feature for this target (ignoring feature)
'+uwu' is not a recognized feature for this target (ignoring feature)
'+uwu' is not a recognized feature for this target (ignoring feature)
'+uwu' is not a recognized feature for this target (ignoring feature)
'+uwu' is not a recognized feature for this target (ignoring feature)
'+uwu' is not a recognized feature for this target (ignoring feature)
'+uwu' is not a recognized feature for this target (ignoring feature)
'+uwu' is not a recognized feature for this target (ignoring feature)
'+uwu' is not a recognized feature for this target (ignoring feature)
'+uwu' is not a recognized feature for this target (ignoring feature)
'+uwu' is not a recognized feature for this target (ignoring feature)
warning: 1 warning emitted
target features have the same effect
trying with target-cpu i get similar spam but not just that, i also get UB in LLVM!
'+uwu' is not a recognized processor for this target (ignoring processor)
'+uwu' is not a recognized processor for this target (ignoring processor)
'+uwu' is not a recognized processor for this target (ignoring processor)
'+uwu' is not a recognized processor for this target (ignoring processor)
'+uwu' is not a recognized processor for this target (ignoring processor)
'+uwu' is not a recognized processor for this target (ignoring processor)
'+uwu' is not a recognized processor for this target (ignoring processor)
'+uwu' is not a recognized processor for this target (ignoring processor)
'+uwu' is not a recognized processor for this target (ignoring processor)
'+uwu' is not a recognized processor for this target (ignoring processor)
'+uwu' is not a recognized processor for this target (ignoring processor)
'+uwu' is not a recognized processor for this target (ignoring processor)
'+uwu' is not a recognized processor for this target (ignoring processor)
'+uwu' is not a recognized processor for this target (ignoring processor)
'+uwu' is not a recognized processor for this target (ignoring processor)
'+uwu' is not a recognized processor for this target (ignoring processor)
'+uwu' is not a recognized processor for this target (ignoring processor)
'+uwu' is not a recognized processor for this target (ignoring processor)
'+uwu' is not a recognized processor for this target' (ignoring processor)
+uwu' is not a recognized processor for this target' (ignoring processor)
+uwu'' is not a recognized processor for this target+uwu (ignoring processor)
' is not a recognized processor for this target (ignoring processor)
'+uwu' is not a recognized processor for this target (ignoring processor)
'+uwu' is not a recognized processor for this target (ignoring processor)
LLVM ERROR: 64-bit code requested on a subtarget that doesn't support it!
'+uwu' is not a recognized processor for this target (ignoring processor)
pure virtual method called
terminate called without an active exception
fish: Job 1, 'rustc +stable -Ctarget-cpu=+uwu…' terminated by signal SIGABRT (Abort)
it's unreliable. sometimes everything is fine, sometimes it aborts and sometimes it segfaults.
This same error spam reproduces if using an intentionally bad target, like
RUSTFLAGS='-C target-cpu=xxx-todo'
.`fn main() {}
on x86_64 macOS.
compiling with:
The current output is:
Ideally the output should look like:
something less spammy.
meta
background
I accidentally copy-and-pasted the
RUSTFLAGS
example for-C target-cpu=
from https://rust-lang.github.io/packed_simd/perf-guide/target-feature/rustflags.html#target-cpu in an attempt to compile fortarget-cpu=native
.It looks like x86_64 Darwin doesn't like the
cortex-a75
CPU type and I got a lot of unexpected output before the build errored out in LLVM.