https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94973
--- Comment #3 from DB <db0451 at gmail dot com> --- > Please read https://gcc.gnu.org/bugs and provide the missing information. Fair point. Let me know if I missed anything still. the exact version of GCC; g++.exe (Rev2, Built by MSYS2 project) 9.3.0 the system type; Windows, g++ provided by MSYS2/MinGW64 projects the options given when GCC was configured/built; I didn't build it. Is there a switch that can get this for you? the complete command line that triggers the bug; g++ -I /home/ME/.local/include/range-v3 -std=c++17 -Wall -Wextra -Wpedantic test.cpp the compiler output (error messages, warnings, etc.); already included. the preprocessed file (*.i*) that triggers the bug, generated by adding -save-temps to the complete compilation command I will attach this next. > Why is this marked as a libstdc++ bug? I chose libstdc++ because I figured it was more likely that some corner case of std::invoke() was ultimately being hit, rather than the core compiler being at fault. I guess not. > I can't reproduce this using range-v3 0.10.0 and GCC 9.3.0 on GNU/Linux, the > example compiles fine. Curioser and curioser. It's fine on clang++ on Windows too. Seems a corner case.
