Hi Jim!
On Mon, Nov 18, 2013 at 1:33 AM, Jim Michaels wrote:
> Hi.
> I noticed that c++ templates define types using the keyword class,
However (as of a while ago), you can also use the keyword "typename"
for this purpose, i.e. "template void template_function ...",
and the like.
> and then
> y
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
f
Hi.
I noticed that c++ templates define types using the keyword class, and then you
use them you plug in the data type, like double.
is double actually a class? does it have data members I can look at? because if
it does, I would like to see how to access them. specifically, I want the
value. I
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/
___
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 bui
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 - bui
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 f
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
> #Include
> #include
> #include
> #include
>
>
> typedef uint64_t addressType; //with 64-bit boxes, there may be
> su
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 solu
what's going on? GlobalMemoryStatusEx() always returns failure. I even memset()
the struct with 0's, no difference.
#include
#Include
#include
#include
#include
typedef uint64_t addressType; //with 64-bit boxes, there may be support for
__int128, but I guess not yet with some compilers
t
> 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 rebas
or comment in /etc/pacman.conf mingw repository
17 нояб. 2013 г., в 22:15, Alexpux написал(а):
>
> 17 нояб. 2013 г., в 22:13, Jon написал(а):
>
>>
>> On Sun, Nov 17, 2013 at 1:06 PM, Jon wrote:
>> $ pacman -Syu
>> :: Synchronizing package databases...
>> msys 75.5 K
17 нояб. 2013 г., в 22:13, Jon написал(а):
>
> On Sun, Nov 17, 2013 at 1:06 PM, Jon wrote:
> $ pacman -Syu
> :: Synchronizing package databases...
> msys 75.5 KiB 337K/s 00:00
> [] 100%
> :: Starting full system upgrade...
> resolving de
On Sun, Nov 17, 2013 at 1:06 PM, Jon wrote:
> $ pacman -Syu
> :: Synchronizing package databases...
> msys 75.5 KiB 337K/s 00:00
> [] 100%
> :: Starting full system upgrade...
> resolving dependencies...
> looking for conflicting packages...
17 нояб. 2013 г., в 22:06, Jon написал(а):
> $ pacman -Syu
> :: Synchronizing package databases...
> msys 75.5 KiB 337K/s 00:00
> [] 100%
> :: Starting full system upgrade...
> resolving dependencies...
> looking for conflicting packages..
$ pacman -Syu
:: Synchronizing package databases...
msys 75.5 KiB 337K/s 00:00
[] 100%
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...
Packages (4) bash-4.2.045-3 mpfr-3.1.2.p4-1 msys2-base-1
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. I've
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 pt
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
2013/11/17 Victor Bombi
> Hello,
>
> Is there any way from the compiler's point of view to know is we are
> compiling with pthreads or winpthreads (#define or any other way)
>
winpthreads is a pthreads implementation. I'm afraid I don't understand
your question. What are you trying to accomplish
Hello,
Is there any way from the compiler's point of view to know is we are
compiling with pthreads or winpthreads (#define or any other way)
victor
--
DreamFactory - Open Source REST & JSON Services for HTML5 & Nativ
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,
>
> Pl
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
23 matches
Mail list logo
