aboutsummaryrefslogtreecommitdiff
path: root/gcc/d/expr.cc
diff options
context:
space:
mode:
authorAlexandre Oliva <oliva@adacore.com>2022-06-23 23:20:45 -0300
committerAlexandre Oliva <oliva@gnu.org>2022-06-23 23:20:45 -0300
commitc655ff35eda02dc53cf8dc9a98208ce8a4604a1f (patch)
tree0eb1044821f0d68efb20348079f12cb7fa70fdcd /gcc/d/expr.cc
parentdf724ec773d63b2efc4010a7e31280eeb51ee2ce (diff)
downloadgcc-c655ff35eda02dc53cf8dc9a98208ce8a4604a1f.zip
gcc-c655ff35eda02dc53cf8dc9a98208ce8a4604a1f.tar.gz
gcc-c655ff35eda02dc53cf8dc9a98208ce8a4604a1f.tar.bz2
aarch64: testsuite: symbol-range fallback to compile
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. Still, linking may be useful, so introduce a two_plus_gigs effective target, that checks for the ability to link a program with 2GiB of sbss, and use that to select whether to link or just compile symbol-range.c. for gcc/ChangeLog * doc/sourcebuild.texi (Environment attributes): Document two_plus_gigs. for gcc/testsuite/ChangeLog * lib/target-supports.exp (check_effective_target_two_plus_gigs): New. * gcc.target/aarch64/symbol-range.c: Link only on two_plus_gigs targets, compile otherwise.
Diffstat (limited to 'gcc/d/expr.cc')
0 files changed, 0 insertions, 0 deletions