aboutsummaryrefslogtreecommitdiff
path: root/lldb/packages/Python/lldbsuite/test/gdbclientutils.py
diff options
context:
space:
mode:
authorYounan Zhang <zyn7109@gmail.com>2025-10-14 14:24:34 +0800
committerGitHub <noreply@github.com>2025-10-14 14:24:34 +0800
commit5a560b306dbc93c5f9dde3a0a4e39d5d56a287dc (patch)
treeb9958b373bbccd6aed6e993f92325bc16b08baa5 /lldb/packages/Python/lldbsuite/test/gdbclientutils.py
parent401308fc163521bffd700a2c55e88074148de404 (diff)
downloadllvm-5a560b306dbc93c5f9dde3a0a4e39d5d56a287dc.zip
llvm-5a560b306dbc93c5f9dde3a0a4e39d5d56a287dc.tar.gz
llvm-5a560b306dbc93c5f9dde3a0a4e39d5d56a287dc.tar.bz2
Revert "[Clang] Preserve more sugars in constraint evaluation" (#163322)
Reverts llvm/llvm-project#162991 That patch breaks certain uses of VLAs when combined with constrained types. This is a pre-existing issue that occurs when concepts are instantiated with sugar. See also #102353 and related PRs. I tried to fix it on top of the status quo in #163167, but that approach turned out to be unfeasible, and our maintainer was clearly unhappy with it, hence this revert. Even after this patch, some VLA uses remain broken on trunk (see the example below), because our normalization patch depends on sugar to correctly compile libc++, due to a very subtle underlying bug. Still, this is the best attempt to mitigate the problem for now. We discussed this and agreed that the long-term solution is to remove the sugar dependencies from concepts, before the VLA issue is properly resolved through a larger refactoring. I'll add a related test (which passes with partially applied sugar) after this revert, since I don't have a reduced example yet.
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/gdbclientutils.py')
0 files changed, 0 insertions, 0 deletions