When evaluating asm operands it must be known if they correspond
to a memory operand or not. This is done by looking at the constraint.
In most case it's enough to look at the common constraints but
PPC & S390 have some specific constraints for memory operands.
Other kinds of operands may also need arch-specific constraints.
This series adds support for processing arch-specific constraints
and let sparse know about PPC & S390 constraints for memory operands.
Luc Van Oostenryck (3):
add support for arch specific asm constraints
add memory asm constraint for PPC
add memory asm constraint for S390
evaluate.c | 5 ++++-
target-ppc.c | 13 +++++++++++++
target-s390.c | 13 +++++++++++++
target.h | 3 ++-
4 files changed, 32 insertions(+), 2 deletions(-)
--
2.27.0
