Re-commit: [hexagon] Distinguish the 'o', 'v', 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.

No functional change intended.

Reviewers: kparzysz, adasgupt

Reviewed By: kparzysz, adasgupt

Subscribers: colinl, llvm-commits

Differential Revision: http://reviews.llvm.org/D8204

Like for the PowerPC target, I've had to add 'i' to the constraint mappings in
order to pass 2007-12-17-InvokeAsm.ll. It's not clear why 'i' has historically
been treated as a memory constraint.



git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@232480 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
Daniel Sanders
2015-03-17 14:37:39 +00:00
parent 99739705ac
commit 42c951a74c
3 changed files with 10 additions and 6 deletions

View File

@ -243,7 +243,7 @@ public:
Constraint_i,
Constraint_m,
Constraint_o,
Constraint_v, // Unused at the moment since Constraint_m is always used.
Constraint_v,
Constraint_Q,
Constraint_Z,
Constraint_Zy,