On Apr 11 12:16, Corinna Vinschen wrote: > On Apr 10 18:16, Corinna Vinschen wrote: > > On Apr 10 16:49, Dave Korn wrote: > > > On 10/04/2013 10:57, Yaakov (Cygwin/X) wrote: > > > > > > > Could you explain the necessity of the dllimport's in the same patch? > > > > > > The idea is to one day be able to move away from having auto-import > > > enabled > > > by default in binutils, so that .rdata can go back into the > > > read-only-mapped > > > .rdata section and be shared between processes as it ought. > > > > Doesn't that affect applications which use something like > > > > extern int optind; > > > > in their code? Kai did quite a job to get this working on x86_64 by > > implementing the medium/large code models for x86_64, and Cygwin's > > x86_64 gcc uses the medium code model by default. Disabling this again > > would be rather counterproductive. > > What about this issue? If the idea is to revert all automatism which > allows to declare external variables in DLL s without dllimport, then > I don't think that's a good idea for Cygwin. > > If I misunderstand the issue, please say so.
Oh, and, btw., I don't quite understand "so that .rdata can go back into the read-only-mapped .rdata section" Typo? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat
