Re-commit: [hexagon] Distinguish the 'o', 'v', and 'm' inline assembly memory constra...
authorDaniel Sanders <daniel.sanders@imgtec.com>
Tue, 17 Mar 2015 14:37:39 +0000 (14:37 +0000)
committerDaniel Sanders <daniel.sanders@imgtec.com>
Tue, 17 Mar 2015 14:37:39 +0000 (14:37 +0000)
commit42c951a74c9cebe42adc2508f7074f1106b9fb3c
tree22695a3bbea33e64b27307942a1af3e7d4b2888b
parent99739705ac73470caebdcce6fe6e0edc829c74a0
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
include/llvm/IR/InlineAsm.h
lib/Target/Hexagon/HexagonISelDAGToDAG.cpp
lib/Target/Hexagon/HexagonISelLowering.h