https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105608
--- Comment #11 from Lewis Hyatt <lhyatt at gcc dot gnu.org> --- Oh interesting. So the purpose of this test was just to record that GCC outputs incorrect locations for this case, I wanted to xfail it and then fix it properly for GCC 15. I did not consider that it might output different wrong locations for different platforms, but I could buy that it may happen, for a similar reason why this switched from being silently broken to ICEing since r11-338 which was seemingly unrelated. It seems like in one case the wrong location is inside the header file and in the other case, the wrong location is the line just following the include. It may have to do with line endings or some other issue with the treatment of EOF? If this test is causing problems we could just skip it on some architectures maybe? Once the underlying issue is fixed, the location (line 2 of the .C file) will be correct everywhere. I am curious why it gets a different wrong output though, if there is a compile farm machine with this architecture I could look into it.
