Displaying 4 results from an estimated 4 matches for "l_x".
Did you mean:
_x
2009 Jul 03
0
A fast version of ccf () accepting missing values ?
...=na.pass" to the ccf() function.
So, I wrote a naive function of my own (see below).
Unsurprisingly, this function is not very fast.
Do you think that it is possible to do better, or should I accept my fate
?
Bruno.
my_ccf <- function (X, Y, lag.before = NULL, lag.after = NULL) {
l_X <- length(X)
l_Y <- length(Y)
if (l_Y != l_X) {
cat ("X and Y should have same size !")
return
}
if (is.null(lag.before)) {
lag.before <- l_X / 10
#should do 10*log10(N/m)
}
if (is.null(lag.after)) {
lag.after <- l_X / 10
# idem lag.before...
2009 Jun 16
0
[LLVMdev] PIC documentation ?
...esults on x86-32 with -fomit-frame-pointer (which is not the default):
result of -fPIC (equivalent to -fpic on Darwin):
_foo:
call L3
"L00000000001$pb":
popl %ecx << gets value of PC into %ecx
(other registers can be used)
movl L_x$non_lazy_ptr-"L00000000001$pb"(%ecx), %eax <<
gets &x; PC relative
movl (%eax), %eax << gets x; indirect
ret
.comm _x,4,2
.section __IMPORT,__pointers,non_lazy_symbol_pointers
L_x$non_lazy_ptr:
.indirect_symbol _x <&l...
2009 Jun 16
4
[LLVMdev] PIC documentation ?
Anton,
>> Can I ask what platform ABI's are documented other than Itanium ?
> I'd bet all platform ABI are more or less documented.
Right.
Maybe we should collect references and do some LLVM PIC documentation and
put it on LLVM website ?
>> I need to get to understand PIC on x86, x86_64 and PowerPC for the COFF
>> and MachO backends.
> ABI is normally induced
2002 Oct 18
7
RAM usage
Hi,
I'm having problems while working with large data sets with R 1.5.1 in
windows 2000. Given a integer matrix size of 30 columns and 15000 rows
my function should return a boolean matrix size of about 5000 rows and
15000 columns.
First of all I tried to run this function on computer with 256 MB of
RAM. I increased memory limit of R with memory.limit() up to 512 MB. I
was inspecting