mirror of
https://github.com/c64scene-ar/llvm-6502.git
synced 2025-07-22 23:24:59 +00:00
[arm] Distinguish the /U[qytnms]/, 'Uv', 'Q', and 'm' inline assembly memory constraints.
Summary: But still handle them the same way since I don't know how they differ on this target. Of these, /U[qytnms]/ do not have backend tests but are accepted by clang. No functional change intended. Reviewers: t.p.northover Reviewed By: t.p.northover Subscribers: t.p.northover, aemerson, llvm-commits Differential Revision: http://reviews.llvm.org/D8203 git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@238921 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
@@ -3920,13 +3920,25 @@ SDNode *ARMDAGToDAGISel::SelectInlineAsm(SDNode *N){
|
||||
bool ARMDAGToDAGISel::
|
||||
SelectInlineAsmMemoryOperand(const SDValue &Op, unsigned ConstraintID,
|
||||
std::vector<SDValue> &OutOps) {
|
||||
assert(ConstraintID == InlineAsm::Constraint_m &&
|
||||
"unexpected asm memory constraint");
|
||||
// Require the address to be in a register. That is safe for all ARM
|
||||
// variants and it is hard to do anything much smarter without knowing
|
||||
// how the operand is used.
|
||||
OutOps.push_back(Op);
|
||||
return false;
|
||||
switch(ConstraintID) {
|
||||
default:
|
||||
llvm_unreachable("Unexpected asm memory constraint");
|
||||
case InlineAsm::Constraint_m:
|
||||
case InlineAsm::Constraint_Q:
|
||||
case InlineAsm::Constraint_Um:
|
||||
case InlineAsm::Constraint_Un:
|
||||
case InlineAsm::Constraint_Uq:
|
||||
case InlineAsm::Constraint_Us:
|
||||
case InlineAsm::Constraint_Ut:
|
||||
case InlineAsm::Constraint_Uv:
|
||||
case InlineAsm::Constraint_Uy:
|
||||
// Require the address to be in a register. That is safe for all ARM
|
||||
// variants and it is hard to do anything much smarter without knowing
|
||||
// how the operand is used.
|
||||
OutOps.push_back(Op);
|
||||
return false;
|
||||
}
|
||||
return true;
|
||||
}
|
||||
|
||||
/// createARMISelDag - This pass converts a legalized DAG into a
|
||||
|
Reference in New Issue
Block a user