Displaying 7 results from an estimated 7 matches for "r_cstackstart".
2016 Feb 01
1
Wrong config check for __libc_stack_end
...39;m
happy for clarification if I misunderstood you) :
The #ifdef ... #elseif ... #else ... # endif
branch which *uses* the __libc_stack_end "variable" would
hopefully be a speedup in comparison with the alternatives; from
system.c mentioned above:
#if defined(HAVE_LIBC_STACK_END)
R_CStackStart = (uintptr_t) __libc_stack_end;
#elif defined(HAVE_KERN_USRSTACK)
{
/* Borrowed from mzscheme/gc/os_dep.c */
int nm[2] = {CTL_KERN, KERN_USRSTACK};
void * base;
size_t len = sizeof(void *);
(void) sysctl(nm, 2, &base, &len, NULL, 0);
R_CStackStart = (uintptr_t) base;
}
#else...
2006 Apr 11
4
Stack checking, core dumps, and embedding R
I will say this first -- I can't copy/paste the error message from the
screen, so it's being retyped. Errors might occur. SORRY.
I've been experiencing some interesting stack warnings recently when
moving from R 2.2.x to the R 2.3.0 series and the R 2.4.0 series. In
particular, I'm getting warnings of "Error: C stack usage is too close
to the limit" before
2016 Feb 01
3
Wrong config check for __libc_stack_end
>>>>> Alba Pompeo <albapompeo at gmail.com>
>>>>> on Fri, 29 Jan 2016 08:23:26 -0200 writes:
> Here is my log from 'make check' using an Intel i5 64-bit
> processor - http://pastebin.com/raw/N6SYAuFX Here is
> Isaac's log from 'make check' using an Intel Atom 32-bit
> processor -
2006 Jul 28
3
R uses private function in libc (PR#9107)
...nux
Submission from: (NULL) (171.66.155.86)
libc used to export the symbol:
__libc_stack_end;
however, newer versions of libc no longer export it. R has some serious
problems around this, because the code has:
# ifdef linux
extern void * __libc_stack_end;
# endif
and
#if defined(linux)
R_CStackStart = (uintptr_t) __libc_stack_end;
#elif defined(HAVE_KERN_USRSTACK)
in r-2.3.1/src/unix/system.c
This code needs to be fixed. It is causing all sorts of problems when trying to
run R across multiple systems with different libc versions.
--Quanah
2006 Nov 15
0
INSTALL R-2.4.0 on Compaq Tru64 UNIX V5.1B
...Defn.h:554: parse error before "R_CStackLimit"
../../src/include/Defn.h:554: warning: type defaults to `int' in
declaration of `R_CStackLimit'
../../src/include/Defn.h:554: warning: data definition has no type or
storage class
../../src/include/Defn.h:555: parse error before "R_CStackStart"
../../src/include/Defn.h:555: warning: type defaults to `int' in
declaration of `R_CStackStart'
../../src/include/Defn.h:555: warning: data definition has no type or
storage class
gmake[3]: *** [dynload.o] Error 1
gmake[3]: Leaving directory `/shs/R-2.4.0/src/unix'
gmake[2]: *** [...
2020 Jun 25
0
R 4.0.1-4.0.2 built with Intel Composer 19.0-19.1.1, error in "make check" on CentOS 7.7
...at the stack size check is somehow skipped. (Perhaps optimized away?)
The evaluation depth limit is checked in src/main/eval.c, line 705 [*],
followed by stack size check. Can you attach the debugger and take a
look at the values of R_EvalDepth and R_Expressions while executing the
text? What about R_CStackStart and R_CStackLimit? What is the stack
size limit (ulimit -s?) on the machine running this test?
--
Best regards,
Ivan
[*]
https://github.com/wch/r-source/blob/8d7ac4699fba640d030703fa010b66bf26054cbd/src/main/eval.c#L705
-------------- next part --------------
A non-text attachment was scrubbed....
2020 Jun 24
5
R 4.0.1-4.0.2 built with Intel Composer 19.0-19.1.1, error in "make check" on CentOS 7.7
Hi there,
I initially asked about this on r-help and was told this might be a better venue. I?m not really convinced from reading the posting guide, but I?ll give it a shot. It was also suggested that the R-Project doesn?t really care about building with ?non-standard? compilers, but I can?t find any evidence of that on the website (indeed, there?s some mention of successful past builds, and the