Techcable 1a32f2a7f4

test_runner: workaround #1923, isolating error traces in tests ...

Essentially #1923 means "caught" errors still show up in error return traces.
The correct fix would require the compiler to fix this, but that could affect performance.

For now, simply workaround this issue by clearing the return traces
between tests.

This means that "caught" errors in one test will not show up in the
error traces of other tests.

2022-08-22 14:38:03 +03:00

..

compiler_rt

stage2: implement @setFloatMode

2022-07-23 15:40:12 +03:00

docs

autodoc: minor pr cleanup

2022-08-18 18:02:19 +02:00

include

move zig.h to become an installation file

2022-07-27 10:26:45 -07:00

init-exe

init-exe template: add flushing to the buffered writer

2022-08-04 21:12:42 +02:00

init-lib

flatten lib/std/special and improve "pkg inside another" logic

2022-05-06 22:41:00 -07:00

libc

update macOS libc headers

2022-07-04 12:14:48 -07:00

libcxx

libcxx: do not include __config_site

2022-07-02 20:40:59 -07:00

libcxxabi

update libcxxabi to llvm 14.0.6

2022-07-01 16:39:29 -07:00

libunwind

update libunwind to llvm 14.0.6

2022-07-01 16:39:31 -07:00

std

Merge pull request #12563 from Vexu/stage2-fixes

2022-08-22 14:32:31 +03:00

tsan

update libcxx, libcxxabi, libunwind, and tsan to llvm 13 rc1

2021-08-16 23:32:13 -07:00

build_runner.zig

flatten lib/std/special and improve "pkg inside another" logic

2022-05-06 22:41:00 -07:00

c.zig

Sema: validate deref operator type and value

2022-07-01 10:22:25 +03:00

compiler_rt.zig

stage2: lower float negation explicitly

2022-06-30 00:02:00 -07:00

ssp.zig

flatten lib/std/special and improve "pkg inside another" logic

2022-05-06 22:41:00 -07:00

test_runner.zig

test_runner: workaround #1923, isolating error traces in tests

2022-08-22 14:38:03 +03:00