Re: [Mingw-w64-public] How to backtrace a crash with gdb on Windows 7

2018-01-18 Thread sisyphus1
-Original Message- From: Hannes Domani via Mingw-w64-public Sent: Thursday, January 18, 2018 10:11 PM To: mingw-w64-public@lists.sourceforge.net Cc: Hannes Domani Subject: Re: [Mingw-w64-public] How to backtrace a crash with gdb on Windows 7 (gdb) run Starting program:

[Mingw-w64-public] internal compiler error

2018-01-18 Thread Matt Sexton via Mingw-w64-public
Hello, x86_64-w64-mingw32-gcc from the mingw64-gcc-7.2.0-1.fc27.x86_64 package on Fedora 27 is reporting the following error in compiling some of our code: internal compiler error: in get_constraint_for_ptr_offset, at tree-ssa-structalias.c:3155 Is this the right place to ask about the bug?

Re: [Mingw-w64-public] linux gcc vs mingw-w64 performance ?

2018-01-18 Thread Liu Hao
On 2018/1/18 9:27, lemonsqueeze wrote: > Ah, found the big one: > Was testing single threaded but code uses __thread thread-local storage > which slows things down a lot on mingw. > > Tried a few alternatives: > - Microsoft TlsGetValue() / TlsSetValue() > - pthread_getspecific() /

Re: [Mingw-w64-public] How to backtrace a crash with gdb on Windows 7

2018-01-18 Thread Hannes Domani via Mingw-w64-public
> (gdb) run > Starting program: C:\_64\comp\mpfr_bug\ggdb\mpfr-4.0.0\tests\tfprintf.exe > [New Thread 4680.0x160c] > > This application has requested the Runtime to terminate it in an unusual > way. > Please contact the application's support team for more information. > repl-vsnprintf.c:358: GNU

Re: [Mingw-w64-public] linux gcc vs mingw-w64 performance ?

2018-01-18 Thread Vincent Torri
On Thu, Jan 18, 2018 at 2:27 AM, lemonsqueeze wrote: > Ah, found the big one: > Was testing single threaded but code uses __thread thread-local storage > which slows things down a lot on mingw. > > Tried a few alternatives: > - Microsoft TlsGetValue() / TlsSetValue() > -

[Mingw-w64-public] How to backtrace a crash with gdb on Windows 7

2018-01-18 Thread sisyphus1
Hi, In the msys2 shell, I'm building gmp (with specific configure args) and then mpfr. But there are 3 crashing tests in the mpfr test suite for which I would like to obtain a backtrace - but so far, all I'm getting is "No stack". In the hope that someone might be able to see how I can