------- 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)
> > I worked on some of the current large file defines in libgfortran.
> 
> I think there are two options:
> 
> a) libgfortran handles Windows large-file support explicitly, i.e. uses
> off64_t, ftello64, fseeko64 explicitly. (For truncation [cf. backspace on
> writing], one might need to do fseeko64 + SetEndOfFile(HANDLE).)
> 
> b) MinGW maps off_t to off64_t etc. when using the -D_FILE_OFFSET_BITS=64
> similar to (some) Unix.
> 
> I think (b) would automatically enable large-file support for libgfortran; Kai
> will discuss this with other MinGW developers.
> (a) would be an option independent of MinGW changes.
> 
> The plan was to wait for the result of the discussion regarding the MinGW
> changes before continuing here.
> 

Hello,

I spoke in team of mingw-w64 and with some of the team of mingw.org about this
issue. On one hand, we have to agree that this kind of feature would ease
porting of POSIX sources to windows, on the other we see here issues in general
compatibility for native win32 applications and wrong assumptions of users
about POSIX and windows native runtime. So we decided for now, that we won't
introduce this macro magic, and it would be best that libgfortran does this
porting for native windows by themself.

Cheers,
Kai


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40812

Reply via email to