mirror of https://github.com/carbon-language/carbon-lang.git synced 2026-09-27 08:30:10 +01:00

Files

T

Jon Ross-Perkins b828093c87 Start checking for a few possible resource exhaustion scenarios for explorer (#2793 )

I couldn't figure out a way to actually hit a reasonable out-of-memory case once I add the maximum interpreter step count. However, the step count limit seems more important.

I've moved the todo stack limit out of function calls because there are plenty of ways to build up the todo stack without any function calls.

Fixes #2791

2023-04-21 15:14:14 -07:00

fail_allocate.carbon

Start checking for a few possible resource exhaustion scenarios for explorer (#2793 )

2023-04-21 15:14:14 -07:00

fail_function_recursion.carbon

Start checking for a few possible resource exhaustion scenarios for explorer (#2793 )

2023-04-21 15:14:14 -07:00

fail_loop.carbon

Start checking for a few possible resource exhaustion scenarios for explorer (#2793 )

2023-04-21 15:14:14 -07:00

fail_type_check_loop.carbon

Start checking for a few possible resource exhaustion scenarios for explorer (#2793 )

2023-04-21 15:14:14 -07:00

README.md

Start checking for a few possible resource exhaustion scenarios for explorer (#2793 )

2023-04-21 15:14:14 -07:00

README.md

Limit tests

These tests check for various limit conditions (such as an infinite loop). The tests collectively disable autoupdate so that tracing isn't enabled, because tracing creates substantial additional overhead.