| Issue |
145349
|
| Summary |
[libc] Tracking progress for adding hermetic testing on baremetal
|
| Labels |
libc
|
| Assignees |
saturn691
|
| Reporter |
saturn691
|
Downstream (https://github.com/arm/arm-toolchain/), I have managed to hack together running hermetic testing of unit tests by LLVM.
```
❯ qemu-system-arm -M mps2-an500 -semihosting -nographic -device loader,file=libc/test/src/stdio/libc.test.src.stdio.printf_test.__hermetic__.__build__ -s -S
[==========] Running 1 test from 1 test suite.
[ RUN ] LlvmLibcPrintfTest.PrintOut
A simple string with no conversions.
1234567890
1234 and more
[ OK ] LlvmLibcPrintfTest.PrintOut
Ran 1 tests. PASS: 1 FAIL: 0
```
In an ideal world, I would like to contribute this upstream, where the embedded build is ran in the post-commit. In order to do this, I will have to do the following.
- [ ] Fix a few bugs with the testing on LLVM-libc
- [ ] Start the mutex implementation
- [ ] Upstream the LLVM-libc support libraries (https://github.com/arm/arm-toolchain/tree/arm-software/arm-software/embedded/llvmlibc-support) into `crt1` and `semihost`.
- [ ] Other things that I may have missed when integrating upstream.
![]()
_______________________________________________
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
