From 224e05378559ab0846cbe9a237e02952fd1bceb4 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jakub=20Ber=C3=A1nek?= Date: Tue, 7 Oct 2025 22:20:53 +0200 Subject: [PATCH] Add debug assertions flag to `cg_gcc` invocation --- src/tests/codegen-backend-tests/cg_gcc.md | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/src/tests/codegen-backend-tests/cg_gcc.md b/src/tests/codegen-backend-tests/cg_gcc.md index aa3377541..ddfc2a382 100644 --- a/src/tests/codegen-backend-tests/cg_gcc.md +++ b/src/tests/codegen-backend-tests/cg_gcc.md @@ -1,12 +1,17 @@ # GCC codegen backend If you ran into an error related to tests executed with the GCC codegen backend on CI, -you can use the following command to run tests locally using the GCC backend: +you can use the following command to run UI tests locally using the GCC backend: ```bash -./x test tests/ui --set 'rust.codegen-backends = ["llvm", "gcc"]' --test-codegen-backend gcc +./x test tests/ui \ + --set 'rust.codegen-backends = ["llvm", "gcc"]' \ + --set 'rust.debug-assertions = false' \ + --test-codegen-backend gcc ``` +If a different test suite has failed on CI, you will have to modify the `tests/ui` part. + Below, you can find more information about how to configure the GCC backend in bootstrap. ## Choosing which codegen backends are built