Don't hard-code gcc-15 in a test script #878

New issue

Open

opened 2026-08-26 05:07:14 -05:00 by gilles-peskine-arm · 0 comments

gilles-peskine-arm commented

2026-08-26 05:07:14 -05:00

(Migrated from github.com)

As time moves forward, eventually, we'll no longer have gcc-15, only some more recent version. (And perhaps older versions, but we don't keep all major versions in our CI.) So we should make that job work even if gcc-15 is not available. At least, if the default gcc is more recent than 15, or if gcc-latest exists and is more recent than 15, use that.

Note that even if gcc-latest is GCC 15 or above, component_test_gcc_latest does not subsume component_test_gcc15_drivers_opt, because the driver build is likely to reveal more problems.

Affects all branches of both TF-PSA-Crypto and Mbed TLS.

When we fixed https://github.com/Mbed-TLS/mbedtls/issues/9814, we added non-regression testing in the form of a test with GCC 15, which was still brand new at the time. We now hard-code `gcc-15` in `tests/scripts/components-compiler.sh`. But what we really mean is that we want a version of GCC that is 15 or above. As time moves forward, eventually, we'll no longer have `gcc-15`, only some more recent version. (And perhaps older versions, but we don't keep all major versions in our CI.) So we should make that job work even if `gcc-15` is not available. At least, if the default `gcc` is more recent than 15, or if `gcc-latest` exists and is more recent than 15, use that. Note that even if `gcc-latest` is GCC 15 or above, `component_test_gcc_latest` does not subsume `component_test_gcc15_drivers_opt`, because the driver build is likely to reveal more problems. Affects all branches of both TF-PSA-Crypto and Mbed TLS.

No milestone

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

gh-Mbed-TLS/TF-PSA-Crypto#878

No description provided.

Rows
Columns