Hi,
such failures a commonly caused by inline-assembler not treating
memory-ref proper. I assume that inline assembler doesn't specify
explicit memory-clobber/modify. Newer gcc versions are here more
strict then older versions.
Kai
2012/2/20 David Cleaver :
> Hello everyone,
>
> I have run int
Hello everyone,
I have run into a very strange problem and I am not sure what might be causing
it. I am compiling the latest svn of gmp-ecm (right now it is 1746) and
depending on whether I insert a few extra print statements or not, one certain
test in gmp-ecm will either run to completion or
On 19/2-2012 11:59 AM, Ruben Van Boxem wrote:
> It really won't work. At all. MSYS is a minimalistic and old Cygwin,
> which is a POSIX software layer on top of Windows. The MSYS Bash is also
> at version 3.2 or something. Cygwin has 4.2 if I'm not mistaken. MinGW
> != MSYS/Cygwin, it's native Win
On Sun, Feb 19, 2012 at 11:59 AM, Ruben Van Boxem
wrote:
> MSYS is a minimalistic and old Cygwin, which
> is a POSIX software layer on top of Windows. The MSYS Bash is also at
> version 3.2 or something. Cygwin has 4.2 if I'm not mistaken. MinGW !=
> MSYS/Cygwin, it's native Win32, without any se
On 2/19/2012 18:35, Christer Solskogen wrote:
> On 19/2-2012 1:49 AM, JonY wrote:
>>
>> Somebody had #define intmax_t long long, likewise for uintmax_t.
>>
>
> Umkai? I haven't done that ;-) Is it the default setting for mingw-w64
> perhaps?
>
No, somewhere in your code does it, not a mingw-w64
2012/2/19 Christer Solskogen
> On 19/2-2012 1:49 AM, JonY wrote:
> >
> > Somebody had #define intmax_t long long, likewise for uintmax_t.
> >
>
> Umkai? I haven't done that ;-) Is it the default setting for mingw-w64
> perhaps?
>
Well, Bash probably does this in its source somewhere.
>
> > Btw,
On 19/2-2012 1:49 AM, JonY wrote:
>
> Somebody had #define intmax_t long long, likewise for uintmax_t.
>
Umkai? I haven't done that ;-) Is it the default setting for mingw-w64
perhaps?
> Btw, why are you building bash for win64? How does that even work?
>
bash is available in MSYS - so I though
δΊ 2012/2/18 8:40, JonY ει:
__forceinline is defined to
extern __inline__ __attribute__((__always_inline__,__gnu_inline__))
static and extern don't play well together.
why we use extern?
I notice some codes will redefine __forceinline to
__attribute__((__always_inline__))inline
--
Best
On Sat, Feb 18, 2012 at 7:56 AM, JonY wrote:
> On 2/18/2012 14:37, Vincent Torri wrote:
>> On Sat, Feb 18, 2012 at 7:08 AM, Vincent Torri
>> wrote:
>>> On Sat, Feb 18, 2012 at 1:40 AM, JonY wrote:
On 2/18/2012 07:45, Vincent Torri wrote:
> hey
>
> i have that code in a header f
