[libcxx-commits] [PATCH] D122598: [libcxx] avoid using anonymous struct with base classes (fixes gcc-12)

[Jorge Gorbe Moya via Phabricator via libcxx-commits]

jgorbe added a comment.

Thanks for the reply! Yes, I've seen some test failures while trying to update our llvm to (closer to) HEAD, and I bisected them to this commit. These were the affected tests:

lldb/test/API/commands/expression/call-function/TestCallStdStringFunction.py.test
lldb/test/API/functionalities/data-formatter/data-formatter-skip-summary/TestDataFormatterSkipSummary.py.test
lldb/test/API/functionalities/data-formatter/data-formatter-stl/generic/list/TestDataFormatterGenericList.py.test
lldb/test/API/functionalities/data-formatter/data-formatter-stl/generic/multimap/TestDataFormatterGenericMultiMap.py.test
lldb/test/API/functionalities/data-formatter/data-formatter-stl/generic/multiset/TestDataFormatterGenericMultiSet.py.test
lldb/test/API/functionalities/data-formatter/data-formatter-stl/generic/optional/TestDataFormatterGenericOptional.py.test
lldb/test/API/functionalities/data-formatter/data-formatter-stl/generic/set/TestDataFormatterGenericSet.py.test
lldb/test/API/functionalities/data-formatter/stringprinter/TestStringPrinter.py.test
lldb/test/API/python_api/sbvalue_persist/TestSBValuePersist.py.test

I believe all of them failed with some string output being replaced by `"Summary Unavailable"`. My first attempt at reproducing it in a plain upstream checkout failed (`ninja check-lldb` showed me lots of errors, both before and after this change, but it's very possible that I was doing something wrong with my local build), so I added the comment here to see if anyone else was experiencing the same problem, or if the problem was in our side. If you're not seeing the problem, that's additional evidence that the problem might be on our side.


Repository:
  rG LLVM Github Monorepo

CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D122598/new/

https://reviews.llvm.org/D122598