https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87689
--- Comment #5 from Segher Boessenkool <segher at gcc dot gnu.org> --- No, doesn't ring bells. But I have some more input: I couldn't get it to fail on powerpc64-linux. It fails on powerpc64le-linux only if the second file is compiled with -O0. As output I get just $ ./87689 |xxd -g1 0000000: 20 20 20 20 20 20 20 20 20 20 20 31 20 20 20 20 1 0000010: 20 20 20 20 20 20 20 32 20 20 20 20 20 20 20 20 2 0000020: 20 20 20 33 20 20 20 20 20 20 20 20 20 20 20 34 3 4 0000030: 20 20 20 20 20 20 20 20 20 20 20 35 20 20 20 20 5 0000040: 20 20 20 20 20 20 20 30 0a 20 00 0a 20 66 6f 6f 0. .. foo 0000050: 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 0000060: 20 0a so no weird characters other than a zero byte.
