But still handle them the same way since I don't know how they differ on
this target.
No functional change intended. Depends on D8173.
Paths
| Differential D8204
[hexagon] Distinguish the 'o', 'v', and 'm' inline assembly memory constraints. ClosedPublic Authored by dsanders on Mar 10 2015, 8:10 AM.
Details
Summary But still handle them the same way since I don't know how they differ on No functional change intended. Depends on D8173.
Diff Detail Event Timelinedsanders retitled this revision from to [hexagon] Distinguish the 'o', 'v', and 'm' inline assembly memory constraints.. dsanders updated this object. dsanders added a parent revision: D8173: Make each target map all inline assembly memory constraints to InlineAsm::Constraint_m. NFC.. Comment Actions One thing I need to mention about this patch. I couldn't tell which additional constraints are supposed to be accepted by clang since the clang implementation currently accepts every possible constraint (HexagonTargetInfo::validateAsmConstraint() always returns true). For now, I've made Hexagon accept 'o', 'v', and 'm' in the backend but I'm happy to correct it if you can tell me which additional constraint codes should be there. This revision is now accepted and ready to land.Mar 10 2015, 10:13 AM
Revision Contents
Diff 21581 include/llvm/IR/InlineAsm.h
lib/Target/Hexagon/HexagonISelDAGToDAG.cpp
lib/Target/Hexagon/HexagonISelLowering.h
|