diff options
| author | bors <bors@rust-lang.org> | 2022-10-20 11:09:41 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2022-10-20 11:09:41 +0000 |
| commit | 4dcf51b08f4e066a7a5dc766edd3ddba09c7adab (patch) | |
| tree | 1bea68fb4df0a54130a690194ec2d6baee4b171a /compiler/rustc_llvm/llvm-wrapper/ArchiveWrapper.cpp | |
| parent | 43de83e02d50c85ccf427ca64c2a0ca2f77161ad (diff) | |
| parent | 845662e1c0f2315980592ef57beb2e087d3c181c (diff) | |
| download | rust-4dcf51b08f4e066a7a5dc766edd3ddba09c7adab.tar.gz rust-4dcf51b08f4e066a7a5dc766edd3ddba09c7adab.zip | |
Auto merge of #2606 - cbiffle:nostdio, r=RalfJung
Magic functions for writing to stdout/stderr. This enables I/O in no_std contexts (or, really, any Miri-specific OS-independent context). Combined with the `abort` intrinsic it should allow a reasonable test framework in no_std. **Question for maintainers:** So, the `no_std` panic test needs work, for two reasons: - First, its stdout includes Miri's whole message about the abort intrinsic having been used. I guess whatever panic handler you use in `std` contexts exits cleanly without triggering this message. Comparing the entire output with backtrace as golden seems fragile. - Second, likely for the same reason, the test framework appears to expect the test to exit successfully, when in fact it exits with status 1 due to the abort. This means the test doesn't actually pass right now. What shall I do there?
Diffstat (limited to 'compiler/rustc_llvm/llvm-wrapper/ArchiveWrapper.cpp')
0 files changed, 0 insertions, 0 deletions
