search for: l77

...at compiles to it- https://github.com/mukul-rathi/bolt/blob/vtable/examples/vtable/foo.bolt <https://github.com/mukul-rathi/bolt/blob/vtable/examples/vtable/foo.bolt> I currently have code (https://github.com/mukul-rathi/bolt/blob/vtable/src/llvm-backend/llvm_ir_codegen/class_codegen.cc#L57:L77 <https://github.com/mukul-rathi/bolt/blob/vtable/src/llvm-backend/llvm_ir_codegen/class_codegen.cc#L57:L77>) that generates the following global Vtable for a class Foo: %_VtableFoo = type { void (%Foo*, i32)* } %Foo = type { %_VtableFoo*, %pthread_t*, i32, i32, i32, i32 } @_VtableFoo = com...

On Wed, Apr 5, 2017 at 2:24 PM, Robert McGehee <rmcgehee at walleyetrading.net> wrote: > Winston, > I had a similar experience to you tracking down an insanely difficult bug > in my R code that "disappeared" whenever slight changes were made to the > script (e.g. like adding cat() statements). In my case, it coincided with > my over-eager compilation of R and its

...kerfile#L76 That's a Debian default a Policy-conforming offical package must use. For Docker you get these from the (prebuild) .deb package, you get it when you do r-devel by hand as they come back in via R CMD CONFIG: https://github.com/rocker-org/rocker/blob/master/r-devel/Dockerfile#L76-L77 You could undo those two lines / set CFLAGS and CXXFLAGS by hand. | I've also compiled R (again, in Docker) and tested with that, and gotten | the same results. It basically uses just `./configure | --without-recommended-packages` | and then `make`. Then these options should not come in. B...

Hello Does anyone know how to get the p values for changepoints in the "changepoint" package? There is guidance in the CRAN vignette https://cran.r-project.org/web/packages/changepoint/changepoint.pdf but I can't make it work to get the p value out... Thanks Nick Wray [[alternative HTML version deleted]]

The two patches attached allow 9p filesystems to be mounted and listed. Note that I did *not* test the new list-9p function, because I don't have a guest with a new enough kernel handy. 9p filesystems are not included in the output of list-filesystems. Because a lot of existing code feeds the output of list-filesystems directly into the input of mount-options, mount-ro or (even worse) plain

I am also philosophically opposed to changing the specification. That said, there's nothing wrong with adding a note to the specification about the common implementations, particularly the reference library. Then, future developers will know both the precise specification and still have the warning that they risk incompatibility by deviating from the reference implementation. I own devices

Hello list. I'm trying to rebuild the 2.6.9.67.0.20.EL kernel, but it fails even without modifications. How did I try it? Created a (non-root) build environment (not a mock ) Installed the kernel.scr.rpm and did a rpmbuild -ba --target=`uname -m` kernel-2.6.spec 2> prep-err.log | tee prep-out.log The build failed at the end: Processing files: kernel-xenU-devel-2.6.9-67.0.20.EL Checking