Re: [Mingw-w64-public] strange gcc 4.8 32bit windows target DLL behaviour

2013-07-13 Thread Dongsheng Song
On Thu, Jul 4, 2013 at 8:40 PM, Dongsheng Song wrote: > 于 2013/7/4 17:18, Kai Tietz 写道: >> 2013/7/4 Dongsheng Song : >>> On 2013/7/4 4:49, Earnie Boyd wrote: On Wed, Jul 3, 2013 at 12:28 PM, Dongsheng Song wrote: > On Thu, Jul 4, 2013 at 12:09 AM, Kai Tietz > wrote: >> That is a

Re: [Mingw-w64-public] strange gcc 4.8 32bit windows target DLL behaviour

2013-07-04 Thread Dongsheng Song
于 2013/7/4 17:18, Kai Tietz 写道: > 2013/7/4 Dongsheng Song : >> On 2013/7/4 4:49, Earnie Boyd wrote: >>> On Wed, Jul 3, 2013 at 12:28 PM, Dongsheng Song wrote: On Thu, Jul 4, 2013 at 12:09 AM, Kai Tietz wrote: > That is a known issue of ld for pe-coff. If at least one symbol is > expo

Re: [Mingw-w64-public] strange gcc 4.8 32bit windows target DLL behaviour

2013-07-04 Thread Kai Tietz
2013/7/4 Dongsheng Song : > On 2013/7/4 4:49, Earnie Boyd wrote: >> On Wed, Jul 3, 2013 at 12:28 PM, Dongsheng Song wrote: >>> On Thu, Jul 4, 2013 at 12:09 AM, Kai Tietz wrote: That is a known issue of ld for pe-coff. If at least one symbol is exported by dllexport, only those symbols a

Re: [Mingw-w64-public] strange gcc 4.8 32bit windows target DLL behaviour

2013-07-04 Thread Dongsheng Song
On 2013/7/4 4:49, Earnie Boyd wrote: > On Wed, Jul 3, 2013 at 12:28 PM, Dongsheng Song wrote: >> On Thu, Jul 4, 2013 at 12:09 AM, Kai Tietz wrote: >>> That is a known issue of ld for pe-coff. If at least one symbol is >>> exported by dllexport, only those symbols are. If there is none, then >>>

Re: [Mingw-w64-public] strange gcc 4.8 32bit windows target DLL behaviour

2013-07-03 Thread Earnie Boyd
On Wed, Jul 3, 2013 at 12:28 PM, Dongsheng Song wrote: > On Thu, Jul 4, 2013 at 12:09 AM, Kai Tietz wrote: >> That is a known issue of ld for pe-coff. If at least one symbol is >> exported by dllexport, only those symbols are. If there is none, then >> all symbols getting exported. >> > > Just f

Re: [Mingw-w64-public] strange gcc 4.8 32bit windows target DLL behaviour

2013-07-03 Thread Dongsheng Song
On Thu, Jul 4, 2013 at 12:09 AM, Kai Tietz wrote: > That is a known issue of ld for pe-coff. If at least one symbol is > exported by dllexport, only those symbols are. If there is none, then > all symbols getting exported. > Just for curious, why 64 bit Windows target not affected ? Why gcc 4.7

Re: [Mingw-w64-public] strange gcc 4.8 32bit windows target DLL behaviour

2013-07-03 Thread Kai Tietz
That is a known issue of ld for pe-coff. If at least one symbol is exported by dllexport, only those symbols are. If there is none, then all symbols getting exported. You can report that to binutils, but I don't see right now a good way to solve that issue. Regards, Kai 2013/7/3 Dongsheng So

[Mingw-w64-public] strange gcc 4.8 32bit windows target DLL behaviour

2013-07-03 Thread Dongsheng Song
Hi, If source files use __attribute__ ((dllexport)) to export symbols, the result DLL looks fine. But if not use __attribute__ ((dllexport)), the result DLL will export an extra symbol 'InterlockedCompareExchange@12'. I had checked the compiled and link files, do not know why. --