The daily build report errors on the commit: /home/cauchy/cross/i686-windows-gcc-4.9/i686-w64-mingw32/include/winbase.h:999: multiple definition of `InterlockedIncrement64' /home/cauchy/obj/i686-w64-mingw32-gcc-4.9/gcc/./gcc/crtbegin.o:cygming-crtbegin.c:(.text+0x200): first defined here emutls_s.o: In function `InterlockedDecrement64':
-- Dongsheng On Tue, Sep 30, 2014 at 10:12 PM, JonY <jo...@users.sourceforge.net> wrote: > On 9/30/2014 18:56, Marat Radchenko wrote: >> On Tue, Sep 30, 2014 at 06:49:42PM +0800, JonY wrote: >>> On 9/28/2014 20:29, Marat Radchenko wrote: >>>> 1. In 6500e4fd, FORCEINLINE in winnt.h was fixed to omit 'extern' >>>> 2. In d66ee5e8, FORCEINLINE was also fixed in ntdef.h >>>> >>> >>> Hi, >>> >>> Sorry about the slow reply, but what does removing extern do? >> >> Removing extern fixes `static FORCEINLINE` functions: function >> can't be static and extern at the same time. >> >>> Should it be: >>> __forceinline static __inline__ __attribute__((__always_inline__)) >>> >>> for all cases? So no actual definitions are ever emitted? >>> >>> >> >> No. Typical forceinline usage is `static FORCEINLINE void foo(bar)`: >> >> If you add `static` to macro, `static` will appear twice on final definition. >> > > Done, removed from master. > > > > ------------------------------------------------------------------------------ > Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer > Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports > Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper > Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer > http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk > _______________________________________________ > Mingw-w64-public mailing list > Mingw-w64-public@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/mingw-w64-public > ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
