Hi,
Noticed when running on x86_64-linux-gnu with `-m32', this test
triggered a different kind of error. Adjusted the test to use a
different register that is common between x86 and x86_64.
Bootstrapped and regression tested on x86_64-linux-gnu/-m32/-mx32,
committed to mainline.
Regards,
Iain.
---
gcc/testsuite/ChangeLog:
* gdc.dg/attr_register2.d: Adjust test.
---
gcc/testsuite/gdc.dg/attr_register2.d | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/gcc/testsuite/gdc.dg/attr_register2.d
b/gcc/testsuite/gdc.dg/attr_register2.d
index 9061a643f31..22c518f9033 100644
--- a/gcc/testsuite/gdc.dg/attr_register2.d
+++ b/gcc/testsuite/gdc.dg/attr_register2.d
@@ -6,6 +6,6 @@ import gcc.attributes;
@register("ebx") extern int var2; // { dg-error "explicit register variable
.var2. declared .extern." }
-@register("r12") __gshared int var3 = 0x2a; // { dg-error "global register
variable has initial value" }
+@register("ebp") __gshared int var3 = 0x2a; // { dg-error "global register
variable has initial value" }
-@register("r12") __gshared int[256] var4 = void; // { dg-error "data type of
.var4. isn.t suitable for a register" }
+@register("ebp") __gshared int[256] var4 = void; // { dg-error "data type of
.var4. isn.t suitable for a register" }
--
2.34.1
