On Nov 1, 2023, at 6:11 PM, Alexandre Oliva <ol...@adacore.com> wrote: > > Several C++ tests fail with --disable-hosted-libstdcxx, whether > because stdc++ext gets linked in despite not being built, because > standard headers are included but that are unavailable in this mode, > or because headers are (mistakenly?) expected to introduce > declarations such as for ::abort, but in this mode they don't. > > This patch introduces an effective target for GCC test, equivalent to > one that's available in the libstdc++-v3 testsuite, and arranges for > all such tests to be skipped when libstdc++-v3 is not hosted. > > This patch was tested with arm-eabi, with libstdc++-v3 configured with > --disable-hosted-libstdcxx, on gcc-13, and with x86_64-linux-gnu > likewise on trunk. In the latter, there are a number of additional > fails that appear to be related, and that I'm yet to investigate, but > this is big enough already, so I figured I'd post this and see whether > the approach is regarded as sound and acceptable before proceeding any > further. WDYT? Ok to install, to deal with other targets > incrementally?
Ick. I wish there were fewer changed lines and not 1 per test case. It feels like we've painted ourselves into a corner. That said, I'd rather have a nice solid game plan that is better and suggest it over this approach but, the best I can think of it something that can notice after the fact during an error, and during error processing, trim or expect, which is awfully vague. So, instead of commenting more, I'd ask if anyone has a nice, good concrete idea and say I want to withdraw from the vague. If someone comes up with something you think is better, easy, smaller and or other goodness and you want to go that direction, I'd encourage that, otherwise, I'll approve this version.
