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
If CFG_DISABLE_OPTIMIZE is set in the environment, and I run ../configure --enable-optimize, I would expect an optimized build. However, this seems to have the effect of building an optimized LLVM but not an optimized rustc. (Doing VERBOSE=1 make rustc-stage1, I see the -O3 flag in the LLVM compile command lines, but no -O flag in the Rust compile commands.) The Makefile.in suggests my suspicion is right:
This seems to be the expected behavior. However, I'd expect CFG_DISABLE_OPTIMIZE to be consistent throughout Rust's build. That is, CFG_DISABLE_OPTIMIZE should disable all optimization if set.
Support negative ints in manual_range_contains
fixes: rust-lang#8721
changelog: Fixes issue where ranges containing ints with different signs would be
incorrect due to comparing as unsigned.
If CFG_DISABLE_OPTIMIZE is set in the environment, and I run
../configure --enable-optimize
, I would expect an optimized build. However, this seems to have the effect of building an optimized LLVM but not an optimized rustc. (DoingVERBOSE=1 make rustc-stage1
, I see the -O3 flag in the LLVM compile command lines, but no -O flag in the Rust compile commands.) TheMakefile.in
suggests my suspicion is right:If this is the intended behavior, it should at least be documented.
The text was updated successfully, but these errors were encountered: