search for: subcalls

...profiling. I have read the help pages Rprof, summaryRprof and consult the R extensions manual, but I still have problems understanding the output. Basically the output consist of self.time and total.time. I have the understanding that total.time is the time spent in a given function including any subcalls or child functions or whatever the technical term for that activity is. In contrasts self.time is the time spent in the function excluding subcalls. Now, in my understanding basically everything in R is functions. I would then guess that for almost any function (except the "atomic ones")...

EDD (https://en.wikipedia.org/wiki/Enhanced_Disk_Drive) is a BIOS INT 13h subcall for communicating the extended size of the boot disk over 8GB to the OS. Since libguestfs doesn't use a boot disk, and the appliance disk is limited to 4GB, and we use virtio-scsi, this is all useless. EDD is also broken currently on RHEL 7.3, see: https://bugzilla.redhat.com/show_bug.cgi?id=1404287 Also the

Hi John, Thanks, but the Bizzaro pipe comes with many flaws though : * It's not a single operator * It has a different precedence * It cannot be used in a subcall * The variable assigned to must be on the right * It doesn't trigger indentation when going to the line * It creates/overwrite a `.` variable in the worksace. And it doesn't deal gracefully with some lazy evaluation edge

...rs and memory? :P Our mid-term plans include looking at multithreading/parallel processing kinds of things, at least for shared memory systems. At the LLVM level, we are interested in _exposing_ parallelism. In the fib example you are using, for example, it is pretty easy to show that all of the subcalls to fib can be run independently of each other (ie, in parallel). Combined with a suitable runtime library (e.g., pthreads), you could imagine an LLVM transformation that allows it to run well on a machine with 10K processors. :) > Actually, maybe the problem is that scince is not ready arround...

Hello, R is a functional language, pipes are not. There are even higher order functions such as [1] and [2]. Besides, packages are part of R, R couldn't live without them. I find pipes a good idea but I also find it better not to have them as part of base R. If you want to use them, load a package, if you don't, don't. This simple. As for your example, compose, there is a

...interested in _exposing_ parallelism. hm... strange. You mean, you going to define explicitly what and how to parallelize? Why then we don't need similar unpleasant things for registers?.. CL> In the fib example you are CL> using, for example, it is pretty easy to show that all of the subcalls to CL> fib can be run independently of each other (ie, in parallel). Combined CL> with a suitable runtime library (e.g., pthreads), you could imagine an CL> LLVM transformation that allows it to run well on a machine with 10K CL> processors. :) Chris, that's clear. But (let's m...

> I see more precisely what you mean, but I don't think it is that > straightforward to generalise the benefits multiple CPU on single host > programming to multiple CPU at multiple hosts. I don't think that both > cases involve the same techniques. you are right, just think of shared memory. > For example, in "single host" configuration you get a very low

Hello again Valery, Valery A.Khamenya wrote: > All benefits, what one could obtain from "LLVM supporting multiple CPU > at single host", one might obtaine from "LLVM supporting multiple CPU > at multiple hosts". Isn't that logical? I see more precisely what you mean, but I don't think it is that straightforward to generalise the benefits multiple CPU on

Dear R-devel, The most popular piping operator sits in the package `magrittr` and is used by a huge amount of users, and imported /reexported by more and more packages too. Many workflows don't even make much sense without pipes nowadays, so the examples in the doc will use pipes, as do the README, vignettes etc. I believe base R could have a piping operator so packages can use a pipe in