search for: whittl

Dear R-users, I am trying to translate a matlab code for calculating the Local Whittle estimator in time series with long memory originally written by Shimotsu and available free in his webpage ( http://www.econ.queensu.ca/pub/faculty/shimotsu/ ) The Matlab code is ======================================================================================= function[r] = whittle(d,x,m)...

Hi, On windows, get_peername works both with connections obtained via start_server, and connections obtained via connect. On linux, get_peername seems to only work with connections obtained via start_server. (I''m using svn HEAD.) I''m wondering which is the intended behavior? (I realize get_peername is less useful for connections obtained via connect, since one should already

hi all, I have a simple question that does power spectral analysis related to capacity dimension, information dimension, lyapunov exponent, hurst exponent. If yes then please show me the way. I am newbie in the world of chaos. Sayonara With Smile & With Warm Regards :-) G a u r a v Y a d a v Senior Executive Officer, Economic Research & Surveillance Department, Clearing

...-pc-linux-gnu" define i32 @fxpadd(i32 %cl) { entry: %0 = zext i32 %cl to i128 %1 = zext i32 %cl to i128 %2 = add i128 %1, %0 br label %L1001510 L1001510: ; preds = %L13400 %vr1484.5 = trunc i128 %2 to i32 ret i32 %vr1484.5 } This code was whittled down from a fixed point math test by bugpoint, and further simplified by hand. The problem did not occur in 2.8. (Removing the trivial branch makes the problem go away.) I'm not sure where to begin debugging it, so any pointers would be appreciated.

...the point where it is allocating gobs of memory: I think I see the problem just from the trace but I will grab the file and check it out. > Also, Kai has been kind enough to send me a copy of his file which > has a > problem only on -8, which I'll be looking into soon. Matt, if you whittle this file down can you make it available also? One more thing I forgot to mention about debugging. The first point of suspicion is the assembly in the decoder. That you can try with 'configure --disable-asm-optimizations' The second is arithmetic overflow in the linear predictor. You can...

So, as 2.6.21-rc1 is approaching, what is the upstream merge status for the paravirt-ops backends? I believe VMI is in Andi's tree, plus or minus some bugfixes that are still being whittled in, but Andi, do you think the VMI code is in good shape for merging? It would be nice for everyone to clarify their upstream plans - is the goal still to get Xen and lguest merged for the next kernel release? Rusty, you mentioned you had a patchset to push, when do you expect to have it rea...

So, as 2.6.21-rc1 is approaching, what is the upstream merge status for the paravirt-ops backends? I believe VMI is in Andi's tree, plus or minus some bugfixes that are still being whittled in, but Andi, do you think the VMI code is in good shape for merging? It would be nice for everyone to clarify their upstream plans - is the goal still to get Xen and lguest merged for the next kernel release? Rusty, you mentioned you had a patchset to push, when do you expect to have it rea...

...nd a bit of LLVM IR syntax. I have a function definition which looks like this in IR: define void @foo(%1* ptr) { ... The C code for foo has a definition that looks like: typedef struct bar_struct bar; ... Definition of struct bar_struct ... void foo(bar *ptr) { ... I can't whittle down a convenient test source file just now; but I'm trying to understand what the syntax of the 'define' above means -- specifically, what does it mean for a parameter to have type '%1*'? What is the semantics here? Inside the body of @foo, there is an SSA variable %1 -- is...

...at can point to the next place to investigate. (also interesting to note Apple's shipped clang doesn't exhibit this behaviour, I had to use my own recent svn tree) $ clang -arch arm -emit-llvm -S -O0 example.c -o arm.bc $ opt -print-after-all -O1 arm.bc I can see where the branch test is whittled down to an 'if true' and then eliminated, but cannot comment as to why this might be. Cheers, -DavidM On 05/06/2013, at 9:50 AM, Carl Norum <carl at lytro.com> wrote: > > On Jun 4, 2013, at 4:42 PM, Tyler Hardin <tghardin1 at catamount.wcu.edu> wrote: >> I was...

Hello, I'm writing an LTO pass and I'd like to be able to duplicate a function (with debugging info). I'm trying to accomplish this with CloneFunction but it's leading to a seg fault in ld. I've whittled down my problem so that it occurs in this small pass [1]. If I run this pass with opt, I get the expected result (i.e. a valid program that calls main twice). If I run the pass during LTO, ld seg faults. Here is a pastebin of when ld seg faults in lldb [2]. If I set the third parameter of C...

On Jun 4, 2013, at 4:42 PM, Tyler Hardin <tghardin1 at catamount.wcu.edu> wrote: > I was suggesting to add it to the function, like > volatile void func(..); > Theoretically, this would tell the compiler not to omit seemingly superfluous calls to func. 'volatile' can't apply to a function, so I'm not sure what you mean. In your example, 'volatile' modifies

...entry: >  %0 = zext i32 %cl to i128 >  %1 = zext i32 %cl to i128 >  %2 = add i128 %1, %0 >  br label %L1001510 > > L1001510:                                         ; preds = %L13400 >  %vr1484.5 = trunc i128 %2 to i32 >  ret i32 %vr1484.5 > > } > > This code was whittled down from a fixed point math test by bugpoint, and further simplified by hand.    The problem did not occur in 2.8. > (Removing the trivial branch makes the problem go away.) > > I'm not sure where to begin debugging it, so any pointers would be appreciated. DAGCombiner::visitADDE l...

I'm getting a SEGV on a FreeBSD 4.8-STABLE box. The client is Solaris 9/SPARC. Both boxes run 2.6.2. The command I'm running is: $ rsync -arHRv --numeric-ids --delete --exclude=/opt/dist/cdrom \ [paths] [server]:[path] If I whittle down what appears in [paths], then it works. $ gdb rsync rsync.core gdb> bt #0 0x280faf0d in strncmp () from /usr/lib/libc.so.4 #1 0x7 in ?? () #2 0x80597f7 in send_file_name (f=-1, flist=0x808a100, fname=0xbfbfe994 "etc/opt/TWWfsw", recursive=1, base_flags=1) at flist.c:...

...\ --with-lockdir=/var/run/samba \ --disable-avahi \ --disable-swat \ --with-cifsmount \ --without-acl-support \ --without-quotas The resulting smbd is about 6663656 in size. I'd love to be able to whittle this down more to stretch my system resource usage. Does anyone have recommendations for alterations that would reduce the ultimate size of the running process?

first, apologies for so many posts yesterday and today. I am wrestling with nls() and nls2(). I have tried to whittle it down to a simple example that still has my problem, yet can be cut-and-pasted into R. here it is: library(nls2) options(digits=12); y= c(0.4334,0.3200,0.5848,0.6214,0.3890,0.5233,0.4753,0.2104,0.3240,0.2827,0.3847,0.5571,0.5432,0.1326,0.3481) x= c(0.3521,0.4334,0.3200,0.5848,0.6214,0.3890,0...

...> definition which looks like this in IR: > >    define void @foo(%1* ptr) { ... > > The C code for foo has a definition that looks like: > >    typedef struct bar_struct bar; >    ... Definition of struct bar_struct ... >    void foo(bar *ptr) { ... > > I can't whittle down a convenient test source file just now; but I'm trying > to understand what the syntax of the 'define' above means -- specifically, > what does it mean for a parameter to have type '%1*'?  What is the semantics > here?  Inside the body of @foo, there is an SSA var...

The following program is whittled down from a much larger program that always works on Intel, and always works on AMD's threadripper with lapply but not mclappy. With mclapply on AMD, all processes go into "suspend" mode and the program then hangs. This bug is replicable on an AMD Ryzen Threadripper 2950X 16-Core...

I have Dovecot 0.99.9.1 compiled from the source, without SSL, running on a Red Hat 9.0 system - EXT3 file system, Pentium Pro 233 MHz, Intel motherboard, 128M RAM, IBM 40Gig 7200 RPM HD. I find reading and searching to be nice and fast, and comparing it with Courier IMAP on a Celeron 824 MHz, I think Dovecot is generally not much slower, which means it may well be faster than Courier in some or

...---------- Obviously, the error can be in ghostscript, not in R. Or it can be that R produces a pdf file that has some slight problems that do not usually show up, except when distilled. Before I get too badly flamed, feel free to ignore this. I am just trying to help. It took me some time to whittle down the program to isolate the problem. R was invoked under OSX via "R --vanilla" and is version 2.8.1. ghostscript is 8.62 (2008-02-29) under OSX. (It should be easy to check whether this also occurs under linux.) /iaw

...> the testcases to a readable scale while still including the > interesting parts. SelectionDAG's setGraphColor method can also > help when graphs get large. Unfortunately, the testcase is about as simple as it can get: a loop with a gather, a multiply and a store. Maybe I can hand-whittle some IR. > And FWIW, there are some significant improvements in the > viewGraph() output in TOT :-). Yeah, I saw that. Unfortunately we won't get it until early next year, probably. :( -Dave