[Bug fortran/40812] Files > 2GB are incorrectly handled on mingw

2009-12-01 Thread burnus at gcc dot gnu dot org
--- Comment #15 from burnus at gcc dot gnu dot org 2009-12-01 17:08 --- Regarding the ftruncate(64) fall back: one should check that it doesn't operate on none character devices (isatty) and set errno to something like EBADF. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40812

[Bug fortran/40812] Files > 2GB are incorrectly handled on mingw

2009-12-01 Thread burnus at gcc dot gnu dot org
--- Comment #14 from burnus at gcc dot gnu dot org 2009-12-01 16:21 --- Some further notes based on the discussion with Kai: ftruncate: Replace by a configure check for "ftruncate64" and a fallback using first "SetFilePointer" and then "SetEndOfFile(_get_osfhandle(fd))". Note: The funct

[Bug fortran/40812] Files > 2GB are incorrectly handled on mingw

2009-09-13 Thread ktietz at gcc dot gnu dot org
--- Comment #13 from ktietz at gcc dot gnu dot org 2009-09-13 08:19 --- (In reply to comment #12) > > > Well, in fact it is MS here. But we on mingw-w64 think at the moment > > > about > > > to add an override option for this by defining _LARGE_FILES > > (In reply to comment #11) > >

[Bug fortran/40812] Files > 2GB are incorrectly handled on mingw

2009-09-08 Thread burnus at gcc dot gnu dot org
--- Comment #12 from burnus at gcc dot gnu dot org 2009-09-08 07:21 --- > > Well, in fact it is MS here. But we on mingw-w64 think at the moment about > > to add an override option for this by defining _LARGE_FILES (In reply to comment #11) > I worked on some of the current large file

[Bug fortran/40812] Files > 2GB are incorrectly handled on mingw

2009-09-07 Thread jvdelisle at gcc dot gnu dot org
--- Comment #11 from jvdelisle at gcc dot gnu dot org 2009-09-07 23:58 --- I worked on some of the current large file defines in libgfortran. Show me a patch of what you want to do. It should be OK. A patch is worth a thousand words. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?i

[Bug fortran/40812] Files > 2GB are incorrectly handled on mingw

2009-09-06 Thread ktietz at gcc dot gnu dot org
--- Comment #10 from ktietz at gcc dot gnu dot org 2009-09-06 20:05 --- (In reply to comment #9) > (In reply to comment #8) > > (In reply to comment #7) > > > (In reply to comment #6) > > > > I think I found the issue within gfortran for mingw. > > > > > > I think you have this backward

[Bug fortran/40812] Files > 2GB are incorrectly handled on mingw

2009-09-06 Thread kargl at gcc dot gnu dot org
--- Comment #9 from kargl at gcc dot gnu dot org 2009-09-06 19:09 --- (In reply to comment #8) > (In reply to comment #7) > > (In reply to comment #6) > > > I think I found the issue within gfortran for mingw. > > > > I think you have this backwards. "the issue within mingw > > for gfo

[Bug fortran/40812] Files > 2GB are incorrectly handled on mingw

2009-09-06 Thread ktietz at gcc dot gnu dot org
--- Comment #8 from ktietz at gcc dot gnu dot org 2009-09-06 18:52 --- (In reply to comment #7) > (In reply to comment #6) > > I think I found the issue within gfortran for mingw. > > I think you have this backwards. "the issue within mingw > for gfortran" would be a better description

[Bug fortran/40812] Files > 2GB are incorrectly handled on mingw

2009-09-06 Thread kargl at gcc dot gnu dot org
--- Comment #7 from kargl at gcc dot gnu dot org 2009-09-06 18:45 --- (In reply to comment #6) > I think I found the issue within gfortran for mingw. I think you have this backwards. "the issue within mingw for gfortran" would be a better description of the issue. It is afterall mingw

[Bug fortran/40812] Files > 2GB are incorrectly handled on mingw

2009-09-06 Thread ktietz at gcc dot gnu dot org
--- Comment #6 from ktietz at gcc dot gnu dot org 2009-09-06 18:07 --- I think I found the issue within gfortran for mingw. The issue is that off_t is for mingw defined as 'long' (like _off_t). There is a 64-bit off64_t, which holds in fact 64-bits and can be used with the ftello64, and

[Bug fortran/40812] Files > 2GB are incorrectly handled on mingw

2009-09-05 Thread fxcoudert at gcc dot gnu dot org
--- Comment #5 from fxcoudert at gcc dot gnu dot org 2009-09-05 10:10 --- I can confirm the issue with Steve's testcase on a (i686-darwin) to (i586-pc-mingw32) cross-compiler, at trunk revision 151373. The issue can even be seen while running the compiled program under wine, which shoul