diff options
| author | Matt Arsenault <Matthew.Arsenault@amd.com> | 2025-09-18 08:21:57 +0900 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-09-18 08:21:57 +0900 |
| commit | d46715aaa0203cc95f3749d386745ae293f0109f (patch) | |
| tree | 3a55e130845b782291ca7db52fc1cbdd71541925 /llvm/lib/CodeGen/MachineOperand.cpp | |
| parent | 18420d833d895f0e90d951a6adbef3e4e663e36a (diff) | |
| download | llvm-d46715aaa0203cc95f3749d386745ae293f0109f.zip llvm-d46715aaa0203cc95f3749d386745ae293f0109f.tar.gz llvm-d46715aaa0203cc95f3749d386745ae293f0109f.tar.bz2 | |
clang: Emit error if assembler fails to construct subtarget (#159219)
We do not have consistent or good error handling of this situation.
Some tools check for errors, some just assert. The backend has no
proper way of reporting an invalid subtarget specification.
MCSubtargetInfo
currently does unreasonable things like spam warnings to errs, and then
silently proceed in an invalid state. I have a patch which starts
returning
null on some invalid subtargets, but all the tools need to start
erroring
cleanly first. I don't think there is a reliable way to test this today.
It
would have to be an incomplete backend. Ideally we would thread through
some kind of error context from the target to report the reason it's
an invalid subtarget.
Diffstat (limited to 'llvm/lib/CodeGen/MachineOperand.cpp')
0 files changed, 0 insertions, 0 deletions