search for: ctl_hw

Displaying 5 results from an estimated 5 matches for "ctl_hw".

Did you mean: ath_hw
2016 May 05
1
R process killed when allocating too large matrix (Mac OS X)
...t decision is made by the kernel and it doesn't expose its thinking about how it feels, it's hard to tell. I couldn't find any API on OS X akin to didReceiveMemoryWarning in iOS, unfortunately. > > You could guess - e.g. by checking the total system memory > > int mib [] = { CTL_HW, HW_MEMSIZE }; > int64_t value = 0; > size_t length = sizeof(value); > sysctl(mib, 2, &value, &length, NULL, 0); > > and comparing it to the sizes involved. However, even that is not foolproof, because it all depends on the other processes' memory usage, swap space size e...
2016 May 05
4
R process killed when allocating too large matrix (Mac OS X)
Hi Simon, thanks for your quick reply. 1) ... so you can reproduce this? 2) Do you know a way how this can be 'foreseen'? We allocate larger matrices in the copula package depending on the user's input dimension. It would be good to tell her/him "Your dimension is quite large. Be aware of killers in your neighborhood"... before the killer attacks. Thanks & cheers,
2016 May 05
0
R process killed when allocating too large matrix (Mac OS X)
...he blue. Since that decision is made by the kernel and it doesn't expose its thinking about how it feels, it's hard to tell. I couldn't find any API on OS X akin to didReceiveMemoryWarning in iOS, unfortunately. You could guess - e.g. by checking the total system memory int mib [] = { CTL_HW, HW_MEMSIZE }; int64_t value = 0; size_t length = sizeof(value); sysctl(mib, 2, &value, &length, NULL, 0); and comparing it to the sizes involved. However, even that is not foolproof, because it all depends on the other processes' memory usage, swap space size etc. There are slightly m...
2004 Sep 10
3
Altivec, automake
I think I've gotten FLAC__lpc_restore_signal() about as good as I'm going to get it. Here's what I have: -a new file, lpc_asm.s, which has the assembly routines -changes to cpu.h, cpu.c, and stream_decoder.c to enable them -changes to configure.in to support the new cpu stuff -a preliminary Makefile.am -maybe something else I'm forgetting Now automake complains that configure.in
2004 Sep 10
2
Altivec, automake
...--- 86,115 ---- #else info->use_asm = false; #endif + #elif defined FLAC__CPU_PPC + info->type = FLAC__CPUINFO_TYPE_PPC; + #if !defined FLAC__NO_ASM + info->use_asm = true; + #ifdef FLAC__USE_ALTIVEC + #if defined __APPLE__ && defined __MACH__ + { + int selectors[2] = { CTL_HW, HW_VECTORUNIT }; + int result = 0; + size_t length = sizeof(result); + int error = sysctl(selectors, 2, &result, &length, 0, 0); + + info->data.ppc.altivec = error==0 ? result!=0 : 0; + } + #else /* __APPLE__ && __MACH__ */ + /* don't know of any other thread-safe...