Skip to content

Conversation

@delcypher
Copy link

This patch makes it possible to detect in LLDB shell and API tests if -fbounds-safety is supported by the compiler used for testing. The motivation behind this is to allow upstreaming #11835 but with the tests disabled in upstream because the full implementation of -fbounds-safety isn't available in Clang yet.

For shell tests when -fbounds-safety is available the clang-bounds-safety feature is available which means tests can be annotated with # REQUIRES: clang-bounds-safety.

API tests that need -fbounds-safety support in the compiler can use the new @skipUnlessBoundsSafety decorator.

rdar://165225507

…supports -fbounds-safety

This patch makes it possible to detect in LLDB shell and API tests if
`-fbounds-safety` is supported by the compiler used for testing. The
motivation behind this is to allow upstreaming swiftlang#11835
but with the tests disabled in upstream because the full implementation
of -fbounds-safety isn't available in Clang yet.

For shell tests when -fbounds-safety is available the
`clang-bounds-safety` feature is available which means tests can be
annotated with `# REQUIRES: clang-bounds-safety`.

API tests that need -fbounds-safety support in the compiler can use
the new `@skipUnlessBoundsSafety` decorator.

rdar://165225507
@delcypher
Copy link
Author

Ignore this. I targeted the wrong repo. The actual PR is llvm#169112

@delcypher delcypher closed this Nov 21, 2025
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.

1 participant