Alexandre Oliva <[email protected]> writes:
> On some of our embedded aarch64 targets, RAM size is too small for
> this test to fit. It doesn't look like this test requires linking,
> and if it does, the -tiny version may presumably get most of the
> coverage without going overboard in target system requirements.
Linking is valuable here because one of the likely failure modes
is an out-of-range relocation.
Could we instead have a new target selector for whether the memory
map includes xGB of RAM? E.g. maybe it could be along similar lines
to check_effective_target_simulator, reading an optional board
property that gives the RAM size.
Thanks,
Richard
>
> Regstrapped on x86_64-linux-gnu, also tested with a cross to
> aarch64-rtems6. Ok to install?
>
>
> for gcc/testsuite/ChangeLog
>
> * gcc.target/aarch64/symbol-range.c: Compile only.
> ---
> gcc/testsuite/gcc.target/aarch64/symbol-range.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/gcc/testsuite/gcc.target/aarch64/symbol-range.c
> b/gcc/testsuite/gcc.target/aarch64/symbol-range.c
> index d8e82fa1b2829..cc68c19ca85d9 100644
> --- a/gcc/testsuite/gcc.target/aarch64/symbol-range.c
> +++ b/gcc/testsuite/gcc.target/aarch64/symbol-range.c
> @@ -1,4 +1,4 @@
> -/* { dg-do link } */
> +/* { dg-do compile } */
> /* { dg-options "-O3 -save-temps -mcmodel=small" } */
>
> char fixed_regs[0x80000000];
