Re: [Mingw-w64-public] Looking for unsigned __int128

2011-02-11 Thread Sisyphus
- Original Message - From: "Jim Michaels" > > 128-bit constants are not allowed in mingw-w64 apparently. they must be > designed into the language. > > I don't know why there isn't a 128-bit data type - there are UUID's on > UNIX, the > MAC, and the equivalent GUID on windows (a 128-bi

[Mingw-w64-public] PostgreSQL builds with MinGW-w64 (Andrew Dunstan)

2011-02-11 Thread Jarrod Chesney
This is fantastic news :-) On 11/02/2011, at 6:58 PM, mingw-w64-public-requ...@lists.sourceforge.net wrote: > Send Mingw-w64-public mailing list submissions to > mingw-w64-public@lists.sourceforge.net > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.sour

Re: [Mingw-w64-public] should MINIDUMP_EXCEPTION_INFORMATION be packed?

2011-02-11 Thread Joel Dice
On Fri, 11 Feb 2011, Ozkan Sezer wrote: On Fri, Feb 11, 2011 at 11:35 AM, Kai Tietz wrote: 2011/2/11 Joel Dice : Hi all, My application uses AddVectoredExceptionHandler to register an exception handler which, if it can't handle the exception, tries to create a mini dump file for later analys

Re: [Mingw-w64-public] Debugger limitations?

2011-02-11 Thread NightStrike
On Fri, Feb 11, 2011 at 9:43 AM, NightStrike wrote: > On Fri, Feb 11, 2011 at 8:22 AM, Paul Leder wrote: >> Executable is 32-bit, and Cygwin/gdb is 32-bit. >> >> The gdb is the current version from Cygwin, which is 6.8.0. The Cygwin >> gcc is 3.4.4. >> >> I compiled with a Linux binary distributi

Re: [Mingw-w64-public] Debugger limitations?

2011-02-11 Thread NightStrike
On Fri, Feb 11, 2011 at 8:22 AM, Paul Leder wrote: > Executable is 32-bit, and Cygwin/gdb is 32-bit. > > The gdb is the current version from Cygwin, which is 6.8.0. The Cygwin > gcc is 3.4.4. > > I compiled with a Linux binary distribution which I downloaded last week > (I don't have access to tha

Re: [Mingw-w64-public] Debugger limitations?

2011-02-11 Thread Paul Leder
Executable is 32-bit, and Cygwin/gdb is 32-bit. The gdb is the current version from Cygwin, which is 6.8.0. The Cygwin gcc is 3.4.4. I compiled with a Linux binary distribution which I downloaded last week (I don't have access to that machine at the moment, but the gcc version is ~4.5.2). Sou

Re: [Mingw-w64-public] Debugger limitations?

2011-02-11 Thread Earnie
Paul Leder wrote: > Should I expect any problems when running gdb/insight on Cygwin, > debugging cross-compiled binaries? > Maybe. > I'm cross-compiling on Linux (-g -O0), and copying the binaries to > Cygwin, together with the same source tree that I used on Linux. When > I run insight on Cygwin

Re: [Mingw-w64-public] megasoft78's personal build(s)

2011-02-11 Thread NightStrike
Stripping doesn't generally increase speed. AFAIK, gcc is built with -O2. On Fri, Feb 11, 2011 at 6:35 AM, Ruben Van Boxem wrote: > Hi, > > I have just discovered megasoft78's personal Win64 multilib build and what I > think is LTO and Graphite enabled. > > I haven't tested anything yet, but I d

[Mingw-w64-public] megasoft78's personal build(s)

2011-02-11 Thread Ruben Van Boxem
Hi, I have just discovered megasoft78's personal Win64 multilib build and what I think is LTO and Graphite enabled. I haven't tested anything yet, but I did notice that the executables under libexec/gcc/// are not stripped. Stripping these from any unneeded symbols reduces their size to about 20%

Re: [Mingw-w64-public] PostgreSQL builds with MinGW-w64

2011-02-11 Thread JonY
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2/10/2011 22:27, Andrew Dunstan wrote: > The PostgreSQL project recently added > support for building with MinGW-w64. > > cheers > > andrew Thanks, PostgreSQL added. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0

Re: [Mingw-w64-public] Debugger limitations?

2011-02-11 Thread Kai Tietz
Hello Paul, 2011/2/11 Paul Leder : > Should I expect any problems when running gdb/insight on Cygwin, > debugging cross-compiled binaries? No, in general this should work, beside that you have to know that file paths to sources can be different between POSIX/MS file-naming. But this can be maybe

Re: [Mingw-w64-public] should MINIDUMP_EXCEPTION_INFORMATION be packed?

2011-02-11 Thread Ozkan Sezer
On Fri, Feb 11, 2011 at 11:35 AM, Kai Tietz wrote: > 2011/2/11 Joel Dice : >> Hi all, >> >> My application uses AddVectoredExceptionHandler to register an exception >> handler which, if it can't handle the exception, tries to create a mini >> dump file for later analysis.  This involves using Mini

Re: [Mingw-w64-public] should MINIDUMP_EXCEPTION_INFORMATION be packed?

2011-02-11 Thread Kai Tietz
2011/2/11 Joel Dice : > Hi all, > > My application uses AddVectoredExceptionHandler to register an exception > handler which, if it can't handle the exception, tries to create a mini > dump file for later analysis.  This involves using MiniDumpWriteDump from > dbghelp.dll, which accepts a pointer t

Re: [Mingw-w64-public] Looking for unsigned __int128

2011-02-11 Thread Jim Michaels
I see it's in _mingw.h #ifndef _INT128_DEFINED #define _INT128_DEFINED #ifdef __GNUC__ #define __int8 char #define __int16 short #define __int32 int #define __int64 long long #ifdef _WIN64 #ifndef __SIZEOF_INT128__ typedef int __int128 __attribute__ ((__mode__ (TI))); #endif #endif #endif /* __GNU

[Mingw-w64-public] should MINIDUMP_EXCEPTION_INFORMATION be packed?

2011-02-11 Thread Joel Dice
Hi all, My application uses AddVectoredExceptionHandler to register an exception handler which, if it can't handle the exception, tries to create a mini dump file for later analysis. This involves using MiniDumpWriteDump from dbghelp.dll, which accepts a pointer to a MINIDUMP_EXCEPTION_INFORMA