Re: [Mingw-w64-public] [Mingwbuilds-users] GlobalMemoryStatusEx still failing

2013-11-17 Thread niXman
Jim Michaels 2013-11-17 11:27: it's returning failure. I have even filled the MEMORYSTATUSEX struct with 0's using memset(). nothing about that function seems to work. Hi, Please repost to mingw-w64-public@lists.sourceforge.net, because MinGW-builds joined MinGW-W64. -- Regards, niXman

Re: [Mingw-w64-public] [Mingwbuilds-users] GlobalMemoryStatusEx still failing

2013-11-17 Thread dw
Are you setting the dwLength member to the size of the structure? dw On 11/17/2013 1:18 AM, niXman wrote: Jim Michaels 2013-11-17 11:27: it's returning failure. I have even filled the MEMORYSTATUSEX struct with 0's using memset(). nothing about that function seems to work. Hi, Please

Re: [Mingw-w64-public] wipthread flag

2013-11-17 Thread Victor Bombi
for using pthread_attr_setschedparam with win32 wipthreads the range goes from +15 to -15 but it seems that other pthread implementatios for win32 have a different range as stated in https://github.com/LuaLanes/lanes/blob/master/src/threading.c so a #define to tell them apart would be necessary

Re: [Mingw-w64-public] wipthread flag

2013-11-17 Thread Victor Bombi
in the last post I meant the range for sched_priority used in pthread_attr_setschedparam. - Original Message - From: Victor Bombi To: mingw-w64-public@lists.sourceforge.net Sent: Sunday, November 17, 2013 12:21 PM Subject: Re: [Mingw-w64-public] wipthread flag for using

[Mingw-w64-public] Microsoft MPI for MinGW-w64

2013-11-17 Thread Alexander Shukaev
Hello, I'd like to share something with the project. I had to do some MPI-based development on Windows lately. Since both MPICH and OpenMPI are officially discontinued for Windows, the only alternative is to use Microsoft MPI from HPC redistributable package. As usual, it comes only for MSVC.

Re: [Mingw-w64-public] MSYS2 mpfr upgrade via pacman error

2013-11-17 Thread Alexpux
17 нояб. 2013 г., в 22:06, Jon jon.for...@gmail.com написал(а): $ pacman -Syu :: Synchronizing package databases... msys 75.5 KiB 337K/s 00:00 [] 100% :: Starting full system upgrade... resolving dependencies... looking for

Re: [Mingw-w64-public] MSYS2 mpfr upgrade via pacman error

2013-11-17 Thread Alexpux
or comment in /etc/pacman.conf mingw repository 17 нояб. 2013 г., в 22:15, Alexpux alex...@gmail.com написал(а): 17 нояб. 2013 г., в 22:13, Jon jon.for...@gmail.com написал(а): On Sun, Nov 17, 2013 at 1:06 PM, Jon jon.for...@gmail.com wrote: $ pacman -Syu :: Synchronizing package

Re: [Mingw-w64-public] MSYS2 mpfr upgrade via pacman error

2013-11-17 Thread Alexpux
17 нояб. 2013 г., в 22:13, Jon jon.for...@gmail.com написал(а): On Sun, Nov 17, 2013 at 1:06 PM, Jon jon.for...@gmail.com wrote: $ pacman -Syu :: Synchronizing package databases... msys 75.5 KiB 337K/s 00:00 [] 100% :: Starting

Re: [Mingw-w64-public] MSYS2 mpfr upgrade via pacman error

2013-11-17 Thread Jon
You need rebase dlls. Close MSYS2 and execute autorebase.bat from msys root directory Will the dlls always need to be rebased after an upgrade? If not, which specific upgrade scenarios will need a rebase? Perhaps a comment added to autorebase.bat summarizing the scenarios that require

[Mingw-w64-public] GlobalMemoryStatusEx always returns failure

2013-11-17 Thread Jim Michaels
what's going on? GlobalMemoryStatusEx() always returns failure. I even memset() the struct with 0's, no difference. #include iostream #Include memory.h #include windows.h #include stdint.h #include WinBase.h typedef uint64_t addressType; //with 64-bit boxes, there may be support for

Re: [Mingw-w64-public] GlobalMemoryStatusEx always returns failure

2013-11-17 Thread Kai Tietz
As said already before. You are using the API of GlobalMemoryStatusEx wrong. Please initialize *after* memset-ing the MEMORYSTATUSEX structure its dwLength member by sizeof (MEMORYSTATUSEX). Your sample doesn't build correct (some none-present types, some typos, etc). So I reduce the shown

Re: [Mingw-w64-public] GlobalMemoryStatusEx always returns failure

2013-11-17 Thread niXman
Jim Michaels писал 2013-11-18 01:12: what's going on? GlobalMemoryStatusEx() always returns failure. I even memset() the struct with 0's, no difference. #include iostream #Include memory.h #include windows.h #include stdint.h #include WinBase.h typedef uint64_t addressType; //with

[Mingw-w64-public] how do I know which mingw-w64 build to use...

2013-11-17 Thread Jim Michaels
if I am going to host x64 but target 32-bit and 64-bit? so far, I have: i686 - 32-bit target cpu x86_64 - 64 bit target cpu 4.8.2 - GCC version release - GCC type posix - threads dwarf - exception rt_v3 - mingw-w64 runtime version rev0 - build revision SEH - is only for 64-bit what? DWARF - only

Re: [Mingw-w64-public] how do I know which mingw-w64 build to use...

2013-11-17 Thread niXman
Jim Michaels писал 2013-11-18 01:43: if I am going to host x64 but target 32-bit and 64-bit? so far, I have: i686 - 32-bit target cpu x86_64 - 64 bit target cpu 4.8.2 - GCC version release - GCC type posix - threads dwarf - exception rt_v3 - mingw-w64 runtime version rev0 - build

Re: [Mingw-w64-public] how do I know which mingw-w64 build to use...

2013-11-17 Thread JonY
On 11/18/2013 05:55, niXman wrote: SEH - is only for 64-bit what? yes. Will be available for 32bit once patent expires next year. DWARF - only for 32-bit what? yes. Dwarf does not work for 64bit, and broken in some cases on 32bit. SJLJ toolchains are multilib and you can build 32 and

Re: [Mingw-w64-public] how do I know which mingw-w64 build to use...

2013-11-17 Thread niXman
JonY 2013-11-18 02:16: Will be available for 32bit once patent expires next year. this is good news! -- Regards, niXman ___ Dual-target(32 64-bit) MinGW-W64 compilers for 32 and 64-bit Windows: http://sourceforge.net/projects/mingw-w64/

Re: [Mingw-w64-public] GlobalMemoryStatusEx always returns failure

2013-11-17 Thread Jim Michaels
I should have said I was using mingw-builds 4.8.2. I assume this is the latest compiler I should use, yes? I tried it with and without memset(). I had to rework my code to make an example you might be able to compile. hmmph. I think as long as I was working on that prime numbers project, it was