Is this error mingw-w64 related or gcc related?
2012/12/19 Алексей Павлов alex...@gmail.com:
On Ruben's 64-bit builds this code is fail too.
2012/12/19 Алексей Павлов alex...@gmail.com:
Hi!
Sorry commit 5494 not the problem in this situation. I have some
research with next example code:
I verify old revisions and this issue is always and on Ruben's
toolchains too that use stable mingw-w64
2012/12/20 Kai Tietz ktiet...@googlemail.com:
Hmm,
as you mentioned that with some older revision of mingw-w64, you don't
have this issue, but with newer you have, I would assume that it is
Well, indeed that issue is funny ... issue is that for x64 the
FLT_EVAL_METHOD is always -1 and default 0 has to be used. Fixed on
trunk at rev 5507.
Regards,
Kai
--
LogMeIn Rescue: Anywhere, Anytime Remote support for
2012/12/20 Kai Tietz ktiet...@googlemail.com
Well, indeed that issue is funny ... issue is that for x64 the
FLT_EVAL_METHOD is always -1 and default 0 has to be used. Fixed on
trunk at rev 5507.
Not to meddle in other people's affairs, but this is probably valuable for
v2 (unless v3 is due
2012/12/20 Ruben Van Boxem vanboxem.ru...@gmail.com:
Not to meddle in other people's affairs, but this is probably valuable for
v2 (unless v3 is due very very soon ;-))
Ruben
Back-merged at rev. 5509.
Cheers,
Kai
--
Hello Ruben,
just want to ask if you already considered to do updates for
winpthread-toolchain (posix-threading)? Recently I fixed a big
regression in winpthread, so I would recomment to provide new releases
of toolchains providing it.
Additionally I got queried on IRC, if there might be a gcc
On 12/20/12, Kai Tietz ktiet...@googlemail.com wrote:
Hello Ruben,
just want to ask if you already considered to do updates for
winpthread-toolchain (posix-threading)? Recently I fixed a big
regression in winpthread,
While you are on the topic, I would suggest that winpthreads be
moved
