summaryrefslogtreecommitdiff
path: root/sim/testsuite/cris/c/ftruncate1.c
diff options
context:
space:
mode:
authorMike Frysinger <vapier@gentoo.org>2021-11-11 00:29:41 -0500
committerMike Frysinger <vapier@gentoo.org>2021-11-26 20:06:55 -0500
commit1214c97666139d06fd1d1301af05844f7771f377 (patch)
tree820e41dfbd93c33a10e3f4f7ea1282a1fac618ef /sim/testsuite/cris/c/ftruncate1.c
parent264dcc17cc4d2252d58bda347dfd78c1b78517da (diff)
downloadbinutils-gdb-1214c97666139d06fd1d1301af05844f7771f377.tar.gz
sim: testsuite: initial support for OS-specific tests
We usually test against the newlib/libgloss environment, but for a few ports that also support Linux apps, we want to test that logic too. A lot of the C code is written such that it works with either newlib/libgloss or glibc/linux toolchains, but we have some tests that end up being Linux-specific. Cris has been using the target tuple as a rough proxy for this (where cris*-*-elf is assumed to be newlib/libgloss, and everything else is glibc/linux), but that is a bit too rough, and it doesn't work in a multitarget build. So lets create a few stub files that we can do compile tests with to detect the different setups, and then let tests declare which one they require (if they require any at all).
Diffstat (limited to 'sim/testsuite/cris/c/ftruncate1.c')
-rw-r--r--sim/testsuite/cris/c/ftruncate1.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/sim/testsuite/cris/c/ftruncate1.c b/sim/testsuite/cris/c/ftruncate1.c
index 46b8756705c..cc213b83a24 100644
--- a/sim/testsuite/cris/c/ftruncate1.c
+++ b/sim/testsuite/cris/c/ftruncate1.c
@@ -1,5 +1,5 @@
/* Check that the ftruncate syscall works trivially.
-#notarget: cris*-*-elf
+#progos: linux
*/
#include <stdio.h>