search for: vecrecs

Hi, I want to write a package where I would use shared memory for some vectors Any suggestion is appreciated... I wonder if the right approach would be to modify add a modified version of the allocVector(SEXPTYPE type, int length) function specifically shared_mem_id = shmget(shared_mem_key, SHM_SIZE, IPC_CREAT);

Dear R-help, I have been trying really hard to generate the following vector given the data (x) and parameter (alpha) efficiently. Let y be the output list, the aim is to produce the the following vector(y) with at least half the time used by the loop example below. y[1] = alpha * x[1] y[2] = alpha^2 * x[1] + alpha * x[2] y[3] = alpha^3 * x[1] + alpha^2 * x[2] + alpha * x[3] ..... below are

Full_Name: Wolfgang Huber Version: R-devel_2005-03-10 OS: alphaev68-dec-osf4.0f Submission from: (NULL) (62.253.128.15) This report concerns allocation of large (>2^31 byte) chunks of memory with R_alloc. I suspect it is a bug/typo but please don't hate me if it's actually a feature: In R, I can happily create large matrices: > a= matrix(0, nrow=191481, ncol=3063) > dim(a) [1]

The Rprofmem facility is currently enabled only if the configuration option --enable-memory-profiling is used. However, the overhead of having it enabled is negligible when profiling is not actually being done, and can easily be made even smaller. So I think it ought to be enabled all the time. I've attached a patch doing this, which also makes a number of other improvements to Rprofmem,

Hi, This problem started as of r73472 ("Merged in the rest of the basic ALTREP framework."); I tested r73471 and it did not exist. I'm building R devel on Ubuntu 16.04.3 LTS (64-bit), with the following flags: CC="gcc -std=gnu99 -fsanitize=address -fno-omit-frame-pointer" CFLAGS="-fno-omit-frame-pointer -g -O2 -Wall -pedantic -mtune=native" and using

Hi, I'm working with a fairly massive data set and I need to allocate memory beyond the 2GB limit. I'm using R 1.5.0 on a SunOS 5.8 machine (16 GB RAM). Has anyone been succesful at patching the code to get rid of the 2GB memory limit? (there are quite a few places in which vsize is an int or tested against INT_MAX). I'll appreciate any guidance you can provide. Thanks. Regards,

Full_Name: John Brzustowski Version: R-devel trunk and R-2.4.0 OS: linux Submission from: (NULL) (76.10.152.79) Here are two minor potential issues in pointer protection stack (PPS) code which could arise in debugging R with valgrind. Only the second could possibly cause a problem in normal use of R, and only under laughably implausible circumstances. (1) valgrind is given a wrong address when

Full_Name: stephen eglen Version: 1.0.0 OS: Unix (OSF/1) Submission from: (NULL) (129.215.238.26) Hi, in the documentation `Writing R Extensions', the section 3.6.1 (handling the effects of garbage collection) has the following typo: Protecting a SEXP pointer protexts ... Should that be `protects'? -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-

...hat R maintains separate areas for fixed and variable sized objects. The first of these is allocated as an array of SEXPRECs assembled in a list using ``cons cells'' (ordered pairs each containing an element of the list and a pointer to the next cell), and the second as an array of VECRECs. The -n option can be used to specify the number of cons cells (each occupying 16 bytes) which R is to use (the default is 200000), and the -v option to specify the size of the vector heap in megabytes (the default is 2). Only integers are allowed for both options. E.g., to read in a t...

...hat R maintains separate areas for fixed and variable sized objects. The first of these is allocated as an array of SEXPRECs assembled in a list using ``cons cells'' (ordered pairs each containing an element of the list and a pointer to the next cell), and the second as an array of VECRECs. The -n option can be used to specify the number of cons cells (each occupying 16 bytes) which R is to use (the default is 200000), and the -v option to specify the size of the vector heap in megabytes (the default is 2). Only integers are allowed for both options. E.g., to read in a t...

...hat R maintains separate areas for fixed and variable sized objects. The first of these is allocated as an array of SEXPRECs assembled in a list using ``cons cells'' (ordered pairs each containing an element of the list and a pointer to the next cell), and the second as an array of VECRECs. The -n option can be used to specify the number of cons cells (each occupying 16 bytes) which R is to use (the default is 200000), and the -v option to specify the size of the vector heap in megabytes (the default is 2). Only integers are allowed for both options. E.g., to read in a t...