I consistently get a segmentation fault on Windows with 0-size xtensor. The source is to be further investigated but I am getting this consistently on Windows on GH Action in a Python module.
I have found this issue in several operations, but most notably xt::argmax(e) segmentation faults whereas std::distance(e.begin(), std::max_element(e.begin(), e.end())) does not.
Note that this has use implication for me. Default functions segmentation faulting:
in the linked issue, I created a minimal reproduction of the issue on godbolt.
I also filed an MSVC bug (link also in issue), which appears to be an incorrect optimization. I wasn't able to follow the advice to fix the problem however
Activity
sg-james commented on Jan 6, 2023
related: #2568
in the linked issue, I created a minimal reproduction of the issue on godbolt.
I also filed an MSVC bug (link also in issue), which appears to be an incorrect optimization. I wasn't able to follow the advice to fix the problem however