Skip to content

Conversation

@Michael137
Copy link

Makes it easier to cherry-pick clang debug-info changes to stable/21.x

@Michael137
Copy link
Author

@swift-ci test

@Michael137
Copy link
Author

@swift-ci test llvm

@delcypher
Copy link

10:04:10  ********************
10:04:10  Failed Tests (5):
10:04:10    Clang :: BoundsSafety/CodeGen/opt-remarks/bounds-safety-ptr-conversion-O0.c
10:04:10    Clang :: BoundsSafety/CodeGen/opt-remarks/ptr-count-assignment-argc-O0.c
10:04:10    Clang :: BoundsSafety/CodeGen/opt-remarks/ptr-count-assignment-const-O0.c
10:04:10    Clang :: BoundsSafety/CodeGen/trap-reasons/ptr_ge_upper_bound-deref-array_subscript-O0.c
10:04:10    Clang :: BoundsSafety/CodeGen/trap-reasons/ptr_lt_lower_bound-deref-array_subscript-O0.c

We need #11739 to fix those.

Michael137 and others added 5 commits November 5, 2025 08:08
…nfo directory (llvm#154311)

This patch works towards consolidating all Clang debug-info into the
`clang/test/DebugInfo` directory
(https://discourse.llvm.org/t/clang-test-location-of-clang-debug-info-tests/87958).

Here we move only the `clang/test/CodeGen` tests.

The list of files i came up with is:
1. searched for anything with `*debug-info*` in the filename
2. searched for occurrences of `debug-info-kind` in the tests

I created a couple of subdirectories in `clang/test/DebugInfo` where I
thought it made sense (mostly when the tests were target-specific).

There's a couple of tests in `clang/test/CodeGen` that still set
`-debug-info-kind`. They probably don't need to do that, but I'm not
changing that as part of this PR.

(cherry picked from commit 3f3bc48)
…ugInfo directory (llvm#154538)

This patch works towards consolidating all Clang debug-info into the
`clang/test/DebugInfo` directory
(https://discourse.llvm.org/t/clang-test-location-of-clang-debug-info-tests/87958).

Here we move only the `clang/test/CodeGenCXX` tests. I created a `CXX`
subdirectory for now because many of the tests I checked actually did
seem C++-specific. There is probably overlap between the `Generic` and
`CXX` subdirectory, but I haven't gone through and audited them all.

The list of files i came up with is:
1. searched for anything with `*debug-info*` in the filename
2. searched for occurrences of `debug-info-kind` in the tests

There's a couple of tests in `clang/test/CodeGenCXX` that still set
`-debug-info-kind`. They probably don't need to do that, but I'm not
changing that as part of this PR.

(cherry picked from commit f2aedc2)
…bugInfo directory (llvm#154781)

This patch works towards consolidating all Clang debug-info into the
`clang/test/DebugInfo` directory
(https://discourse.llvm.org/t/clang-test-location-of-clang-debug-info-tests/87958).

Here we move only the `clang/test/CodeGenObjC` tests.

The list of files i came up with is:
1. searched for anything with `*debug-info*` in the filename
2. searched for occurrences of `debug-info-kind` in the tests

(cherry picked from commit 8fa55a0)
…DebugInfo directory (llvm#154912)

This patch works towards consolidating all Clang debug-info into the
`clang/test/DebugInfo` directory

(https://discourse.llvm.org/t/clang-test-location-of-clang-debug-info-tests/87958).

Here we move only the `clang/test/CodeGenObjCXX` tests.

The list of files i came up with is:
1. searched for anything with `*debug-info*` in the filename
2. searched for occurrences of `debug-info-kind` in the tests

(cherry picked from commit bac8c87)
…4951)

These tests don't work due to limitations in backend support, so it's
better to mark them uniformly unsupported on AIX and z/OS.

(cherry picked from commit f9bd187)
@Michael137 Michael137 force-pushed the clang/move-debug-info-tests-to-21.x branch from 61a5251 to c208eff Compare November 5, 2025 08:09
@Michael137
Copy link
Author

@swift-ci test llvm

@Michael137
Copy link
Author

@swift-ci test

@Michael137 Michael137 merged commit 077bc64 into stable/21.x Nov 5, 2025
5 checks passed
@Michael137 Michael137 deleted the clang/move-debug-info-tests-to-21.x branch November 5, 2025 17:45
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.

4 participants