https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107059
--- Comment #11 from Jakub Jelinek <jakub at gcc dot gnu.org> --- > #include "..." search starts here: > #include <...> search starts here: > /home/seurer/gcc/git/gcc-test/libstdc++-v3/../libgcc > /home/seurer/gcc/git/build/gcc-test/powerpc64le-unknown-linux-gnu/libstdc++- > v3/include/powerpc64le-unknown-linux-gnu > /home/seurer/gcc/git/build/gcc-test/powerpc64le-unknown-linux-gnu/libstdc++- > v3/include > /home/seurer/gcc/git/gcc-test/libstdc++-v3/libsupc++ > /home/seurer/gcc/git/build/gcc-test/./gcc/include > /home/seurer/gcc/git/build/gcc-test/./gcc/include-fixed > /usr/local/include > /usr/include/powerpc64le-linux-gnu > /usr/include Strange, but above /home/seurer/gcc/git/build/gcc-test/./gcc/include-fixed comes before /usr/include/powerpc64le-linux-gnu and from what I can see at least in my glibc headers, there is just #include <bits/floatn.h> and #include <bits/floatn-common.h> rather than #include_next or something similar, so it is unclear why it would pick /usr/include/powerpc64le-linux-gnu/bits/floatn.h rather than /home/seurer/gcc/git/build/gcc-test/./gcc/include-fixed/bits/floatn.h
