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

[Daniel Sanders]

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.


http://reviews.llvm.org/D8204

EMAIL PREFERENCES
  http://reviews.llvm.org/settings/panel/emailpreferences/