[hexagon] Distinguish the 'o', 'v', and 'm' inline assembly memory constraints.


[hexagon] Distinguish the 'o', 'v', and 'm' inline assembly memory constraints.

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

Event Timeline

dsanders added subscribers: kparzysz, adasgupt, Unknown Object (MLST).Mar 16 2015, 9:10 AM


This commit caused failures on the Hexagon builders (e.g. http://lab.llvm.org:8011/builders/llvm-hexagon-elf/builds/16716) but the tests work perfectly for me. Could someone take a look and let me know which value of ConstraintCode caused getInlineAsmMemConstraint() to return InlineAsm::Constraint_Unknown?

I've just realized I'm being stupid :-). The generic tests are testing X86 support for me and Hexagon for the builder. All I have to do is manually run the test with -march=hexagon.