http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56581
--- Comment #5 from Walt Brainerd <walt.brainerd at gmail dot com> 2013-03-10 19:39:42 UTC --- I think that is exactly what they were (wrote a little program to get rid of them). The files were produced by OCR and then edited (not by me), so that is all possible. Thanks for pointing this out to me. The Intel compiler seemed to completely ignore them, but gfortran sometimes bombed and sometimes didn't with f951.exe: out of memory . . . gfortran compiles all the files in the set without a problem now. It is possible that also caused the internal compiler error, but who knows. On Sun, Mar 10, 2013 at 12:24 PM, burnus at gcc dot gnu.org < gcc-bugzi...@gcc.gnu.org> wrote: > > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56581 > > Tobias Burnus <burnus at gcc dot gnu.org> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > CC| |burnus at gcc dot gnu.org > > --- Comment #4 from Tobias Burnus <burnus at gcc dot gnu.org> 2013-03-10 > 19:24:31 UTC --- > (In reply to comment #2) > > After sending the bug report, I discovered another strange thing. > > The first 24? bits of the file are junk that does not show up in any > > editor. "cat" shows a little open rectangle and "od" shows it. > > (These files were sent to me by somebody else.) > > The extra bytes could be a Unicode byte-order marker? Especially under > Windows, > some editors like to insert them: > https://en.wikipedia.org/wiki/UTF-8#Byte_order_mark > > -- > Configure bugmail: http://gcc.gnu.org/bugzilla/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You reported the bug. >
