Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

use ARM_MCS_verified.cmake for MCS build #295

Merged
merged 5 commits into from
Jan 9, 2024
Merged

Conversation

axel-h
Copy link
Member

@axel-h axel-h commented Jan 4, 2024

A test run can be found at axel-h/seL4#131 (with some dummy config for RISCV32/IA32)

@axel-h axel-h requested a review from lsf37 as a code owner January 4, 2024 12:11
@axel-h axel-h force-pushed the patch-axel-6 branch 3 times, most recently from 69e872d to 7aaf973 Compare January 4, 2024 17:59
@axel-h axel-h force-pushed the patch-axel-6 branch 3 times, most recently from 79f3f7a to e204c30 Compare January 5, 2024 09:54
- remove redundancy
- check if config file exists
- remove unnecessary CMake parameters
- use separate build folder for non-MCS and MCS
- improve comments

Signed-off-by: Axel Heider <[email protected]>
@lsf37
Copy link
Member

lsf37 commented Jan 9, 2024

I'm fine with the MCS part, but we should not be putting in dummy files for configurations that are not under verification (as in the test run), because that will look misleading and we use the list of config files in a number of places to define which platforms are verified (so that would then also generate wrong info).

I guess we could leave the options in this script, but just never call them in the build matrix, so when we do verify RV32 at some point, the test will already be there.

In terms of test completeness, compilation for RV32 and x86 32-bit is covered by the simulation tests that also run on each PR, they're just missing from the quicker standalone compile check.

@lsf37 lsf37 merged commit dbb9677 into seL4:master Jan 9, 2024
7 checks passed
@axel-h axel-h deleted the patch-axel-6 branch January 10, 2024 08:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants