Closed
Description
[dependencies]
config = "=0.9.3"
[profile.release]
panic = "abort"
codegen-units = 1
It seems like both the panic setting and codegen-units setting are required.
I don't know what is going on, but LLVM seems to think it's doing something, but it's been doing the same something for the past 30 minutes. perf top
says:
41.22% libLLVM-13-rust-1.57.0-nightly.so [.] llvm::getUniqueExitBlocksHelper<llvm::BasicBlock, llvm::LoopBase<llvm::BasicBlock, llvm::Loop>, llvm::LoopBase<llvm::BasicBlock, llvm::Loop>::getUniq
36.17% libLLVM-13-rust-1.57.0-nightly.so [.] llvm::ScalarEvolution::forgetMemoizedResults
7.01% libLLVM-13-rust-1.57.0-nightly.so [.] llvm::Instruction::getSuccessor
5.58% libLLVM-13-rust-1.57.0-nightly.so [.] llvm::ScalarEvolution::getLoopDisposition
2.63% libLLVM-13-rust-1.57.0-nightly.so [.] llvm::ScalarEvolution::getSCEVAtScope
rustc --version --verbose
:
rustc 1.57.0-nightly (f03eb6bef 2021-10-02)
binary: rustc
commit-hash: f03eb6bef8ced8a243858b819e013b9caf83d757
commit-date: 2021-10-02
host: x86_64-unknown-linux-gnu
release: 1.57.0-nightly
LLVM version: 13.0.0
Metadata
Metadata
Assignees
Labels
Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues.Category: This is a bug.Issue: The compiler never terminates, due to infinite loops, deadlock, livelock, etc.Medium priorityRelevant to the compiler team, which will review and decide on the PR/issue.Performance or correctness regression from one stable version to another.