Re: Using g++ and -m32 option on x86_64 broken

On Jul 1 06:59, Jeffrey Walton wrote: > On Wed, Jul 1, 2015 at 4:29 AM, Corinna Vinschen > wrote: > > Hi Jeffrey, > > > > On Jun 30 21:38, Jeffrey Walton wrote: > >> Cygwin's GCC responds to the -m32 option, but it causes a compile error: > >> > >>expected unqualified-id before ‘__int128’ > >

Re: Using g++ and -m32 option on x86_64 broken

On Wed, Jul 1, 2015 at 4:29 AM, Corinna Vinschen wrote: > Hi Jeffrey, > > On Jun 30 21:38, Jeffrey Walton wrote: >> Cygwin's GCC responds to the -m32 option, but it causes a compile error: >> >>expected unqualified-id before ‘__int128’ >>inline __int128 >> >> If the project does not su

Re: Using g++ and -m32 option on x86_64 broken

Hi Jeffrey, On Jun 30 21:38, Jeffrey Walton wrote: > Cygwin's GCC responds to the -m32 option, but it causes a compile error: > >expected unqualified-id before ‘__int128’ >inline __int128 > > If the project does not support the -m32 option, then it should be > removes so that using i