On windows, the path internal representation is wchar_t, and input/output often goes through utf8 inbetween, which causes extra allocations.
MS STL does the same, so this shouldn't be a standards compliance issue.
Differential D97497
[libcxx] [test] Disable allocation checks in class.path tests on windows mstorsjo on Feb 25 2021, 1:45 PM. Authored by
Details
On windows, the path internal representation is wchar_t, and input/output often goes through utf8 inbetween, which causes extra allocations. MS STL does the same, so this shouldn't be a standards compliance issue.
Diff Detail
Event Timeline
Comment Actions Abandoning this one, D98398 is clearly better, letting us keep a few allocation checks in some files. |
I'm actually confused about this line's intended effect. AFAICT from a quick skim, DISABLE_NEW_COUNT causes MemCounter::disable_checking = true which causes all the functions of the form MemCounter::checkFooBarEq(x) to automatically succeed.
However, this specific test doesn't seem to contain any calls to MemCounter::checkFooBarEq(x)! It's all using malloc_allocator, which is unaffected(?) by DISABLE_NEW_COUNT.
Thoughts?