there are 4 cases: {c,c++} {m32,m64} with 4 different asm outputs

if that is a 'reasonable' situation - then might need to include
ilp64/ip32 in the target spec ...

Both the 32 and 64 bit versions of the Darwin output are correct, so perhaps something like I had originally proposed, but taking into account the __USER_LABEL_PREFIX__:

-/* { dg-final { scan-assembler "movl.*, var" } } */
+/* { dg-final { scan-assembler "movl.*, (_?var|\\(%)" } } */

Reply via email to