Emit an error if the return value is used on subtargets that do not
support them. Previously we were falling back to the DAG on selection
failure, where it would emit this error and then fail again.
Details
Details
- Reviewers
rampitec - Group Reviewers
Restricted Project
Diff Detail
Diff Detail
Event Timeline
llvm/test/CodeGen/AMDGPU/GlobalISel/llvm.amdgcn.raw.buffer.atomic.fadd-with-ret.ll | ||
---|---|---|
8 | Why there is a second message? |
llvm/test/CodeGen/AMDGPU/GlobalISel/llvm.amdgcn.raw.buffer.atomic.fadd-with-ret.ll | ||
---|---|---|
8 | There are 2 cases here that fail, both should get an error |
Comment Actions
Previously we were falling back to the DAG on selection
failure, where it would emit this error and then fail again.
Why is that a problem? Is this just a temporary thing, while you are testing with the fallback to dag enabled?
To put it another way, what's so special about this case that legalization has to fail harder than other cases?
Comment Actions
The permanent solution is to remove the DAG completely so this should have matching behavior
To put it another way, what's so special about this case that legalization has to fail harder than other cases?
It also saves compile time from compiling the function twice
Why there is a second message?