aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDavid Malcolm <dmalcolm@redhat.com>2024-10-15 10:59:48 -0400
committerDavid Malcolm <dmalcolm@redhat.com>2024-10-15 10:59:48 -0400
commitf8dcb559e615dbb4557a23363f9532a3544a7241 (patch)
tree356e04543399e74f31469530f31c0c978828495d
parent80d7032067a3a5b76aecd657d9b35b0a8f5a941d (diff)
downloadgcc-f8dcb559e615dbb4557a23363f9532a3544a7241.zip
gcc-f8dcb559e615dbb4557a23363f9532a3544a7241.tar.gz
gcc-f8dcb559e615dbb4557a23363f9532a3544a7241.tar.bz2
testsuite, jit: fix test-error-pr63969-missing-driver.c
jit.dg/test-error-pr63969-missing-driver.c tries to break PATH and verify that an error is generated when using an external driver. However it does this by unsetting PATH, and so the test could accidentally find the driver if the system supplies a default and the driver happens to be installed in that path (reported as rhbz#2318021). Fix the test by instead setting PATH to a bogus value. gcc/testsuite/ChangeLog: * jit.dg/test-error-pr63969-missing-driver.c (create_code): When breaking PATH, use setenv with a bogus value, rather than unsetenv, in case the system uses a default path that contains the driver binary. Signed-off-by: David Malcolm <dmalcolm@redhat.com>
-rw-r--r--gcc/testsuite/jit.dg/test-error-pr63969-missing-driver.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/gcc/testsuite/jit.dg/test-error-pr63969-missing-driver.c b/gcc/testsuite/jit.dg/test-error-pr63969-missing-driver.c
index 7335223..152e236 100644
--- a/gcc/testsuite/jit.dg/test-error-pr63969-missing-driver.c
+++ b/gcc/testsuite/jit.dg/test-error-pr63969-missing-driver.c
@@ -28,7 +28,7 @@ create_code (gcc_jit_context *ctxt, void *user_data)
/* Break PATH, so that the driver can't be found
by gcc::jit::playback::context::compile ()
within gcc_jit_context_compile. */
- unsetenv ("PATH");
+ setenv ("PATH", "/this/is/not/a/valid/path", 1);
}
void