This happens before we reset the MCContext so that errors are propagated
to users. Without this, some errors are silently ignored even with a
correct error message.
Details
Details
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Unit Tests
Unit Tests
Time | Test | |
---|---|---|
2,560 ms | x64 windows > MLIR.Examples/Toy/Ch6::jit.toy | |
2,510 ms | x64 windows > MLIR.Examples/Toy/Ch7::jit.toy |
Event Timeline
llvm/lib/CodeGen/MachineModuleInfo.cpp | ||
---|---|---|
172–173 | This doesn't seem like a great user experience. Won't we get two errors, something like the following? error: lds: unsupported initializer for address space error: MC error It seems worth adding an LLVMContext API to mark errors as having been reported another way if we don't have plans to unify MCContext / LLVMContext error reporting in the short term. |
Comment Actions
This happens before we reset the MCContext so that errors are propagated to users.
reset -> because?
Perhaps also document the error code change.
This doesn't seem like a great user experience. Won't we get two errors, something like the following?
It seems worth adding an LLVMContext API to mark errors as having been reported another way if we don't have plans to unify MCContext / LLVMContext error reporting in the short term.