search for: simmer

...always suspicious (probably unjustifiably) of all the memory that is reported as "still reachable", so I wanted to check whether there was any difference if I detach(unload=TRUE) the package after all the tests. In a nutshell, I ended up discovering that the following code: ``` library(simmer) simmer() # allocates a C++ object, as in my initial example detach("package:simmer", unload=TRUE) ``` segfaults on Windows, but not on Linux (then I built the example in my initial email to confirm it wasn't simmer's fault). So given that, from your explanation, I should expect...

...ably) of all the memory > that is reported as "still reachable", so I wanted to check whether > there was any difference if I detach(unload=TRUE) the package after > all the tests. > > In a nutshell, I ended up discovering that the following code: > > ``` > library(simmer) > simmer() # allocates a C++ object, as in my initial example > detach("package:simmer", unload=TRUE) > ``` > > segfaults on Windows, but not on Linux (then I built the example in my > initial email to confirm it wasn't simmer's fault). So given that, > from...

I had added a vignette to the coxme package and all worked well locally, but it failed at CRAN.???? The issue is that the vignette involves using coxme for pedigree data, it doesn't work without the kinship2 package, and I hadn't put in the necessary "if (require(...." logic. The question is, how do I make the entire vignette conditional? If the package isn't available,

On 9 August 2018 at 20:37, Tomas Kalibera wrote: | So to answer your original question, this could probably be handled in | Rcpp, Hm. Why do you say that / what did you have in mind? Recall that we do not alter SEXPs or introduce additional additional reference counters -- because we do not think that altering the basic R API for such calls would be a wise strategy. So we do more or less what

Your dates have an incomplete year information with 34. R assumes that 00-68 are 2000 to 2068 and 69 to 99 are 1969 to 1999. See ?strptime and the details for %y. You can either append ?19? to the start of your year variable to make it completely express the year or check if the date is in the future (assuming all dates should be in the past) and subtract 100 years from the date. > On Dec

Hi all, I?m struggling to get the dates in proper format. I have dates as factors and is in the form 02/27/34( 34 means 1934). If I use as.Date with format %d%m%y it gets converted to 2034-02-27. I tried changing the origin in the as.Date command but nothing worked. Any help is appreciated. Thanks, Ramesh

...Majnemer - Google An update on Clang-based C++ Tooling, Daniel Jasper - Google, Manuel Klimek - Google Session #8: October 30 2:00-3:30 Salon III & IV LLVM for a managed language: what we've learned, Sanjoy Das - Azul Systems, Philip Reames - Azul Systems LLVM back end for HHVM/PHP, Brett Simmers - Facebook, Inc., Maksim Panchenko - Facebook, Inc Session #9: October 30 2:00-3:30: Salon I & II Throttling Automatic Vectorization: When Less Is More, Vasileios Porpodas - University of Cambridge LoopVersioning LICM, Ashutosh Nema - AMD Session #10: October 30 4:30-6:00 Salon III & IV...

On 9/8/15 9:35 AM, Philip Reames wrote: > On the VM state synching side of things, I'm curious about the tradeoffs > involved in the approach you've used. I'm guessing from what you said > that you're essentially pre-reserving a set of allocas for the spill > locations, somehow registering those with your runtime once, then > emitting stores down the unlikely path

Dear Colleagues, I would like to provide a CITATION file for my package nat.nblast [1]. I have the correct citation in BibTeX format [2]. How can I convert this BibTeX to the format needed by R for a package CITATION file (I have a lot of other packages needing citations ...). I think what I need is the opposite of RefManageR::toBiblatex [3]. This seems like it should be a common need, so I

I'm part of a team working on adding an llvm codegen backend to HHVM (PHP JIT, http://hhvm.com) using MCJIT. We have a code layout problem and I'm looking for opinions on good ways to solve it. The short version is that the memory we emit code into is split into a few different areas, and we'd like a way to control which area each BasicBlock ends up in during codegen. I know this

On 9/4/15 1:12 AM, Sanjoy Das via llvm-dev wrote: > Specifically on "Location records" -- > > Is it legal for the optimizer to drop the `!locrec` metadata that you > attach to instructions? The general convention in LLVM is that > dropping metadata should not affect correctness, and if the location > record information is not best-effort or optional then metadata is

On 10/10/2017 11:22 AM, Mark Haney wrote: > > We have this discussion on every list I've ever been, or currently are > on about every 6 months or so.? I do my best to contribute to the list > as often as I can, but I can't help people when they are deadset on > doing dangerous things.? Posts like his, and posts like yours make it > harder for me to bother trying to

...n directory persistence is, to my mind at > least, its own brand of immaturity and will typically cause the person > so being attacked to go on the defensive and harden their stance, and > this is the textbook genesis of a flame. I do agree, to a point.? Being Irish, my temper is always simmering, usually over ignorance or willful stupidity.? But, sometimes you just have to be the bad guy when people are recalcitrant.? Hence my stance in this thread.? I honestly have no problem being the bad guy if I have to be.? In this case, it was a situation where OP was already on the defensive...

On Friday, 26 June 2020 10.47.13 WEST I?aki Ucar wrote: > I used bcond locally and wrongly assumed that fedpkg build would > support --with BCOND and --without BCOND. Instead, the way to activate > it is to change to "%bcond_with check" and then revert to > "%bcond_without check". The only difference with bootstrap is that > "bootstrap" is recognized

...ads. The most advanced example uses like two or three GEPs/loads in a row and I have already explained at the top of the document that the user should not worry - most commonly two or three LLVM IR instructions will be coalesced into a single instruction after optimization. I'll let your idea simmer a bit and see what comes up. For now, I have had the joy of coding up quite a few snippets in LLVM IR. I am learning to swim as I am sinking into all the intricacies of LLVM IR. So far is has only been pleasant working with LLVM IR, albeit I am a tad tired of typing types because LLVM IR demands...

I'm largely with Gabriel Becker on this one: if pipes enter base R, they should be a well thought out and integrated part of the language. I do see merit though in providing a pipe in base R. Reason is mainly that right now there's not a single pipe. A pipe function exists in different packages, and it's not impossible that at one point piping operators might behave slightly different

On 9/8/15, 9:35 AM, "Philip Reames" <listmail at philipreames.com> wrote: >On 09/04/2015 11:36 AM, Brett Simmers via llvm-dev wrote: >> On 9/4/15 1:12 AM, Sanjoy Das via llvm-dev wrote: >>> Specifically on "Location records" -- >>> >>> Is it legal for the optimizer to drop the `!locrec` metadata that you >>> attach to instructions? The general convention i...

...gt;<font face=3D"Verdana, Arial, Helvetica, sans-serif" size=3D= "2">W<buckhorn>atch Wrinkl<curvaceous>es Disap<copeland>pear</font></strong></li> </ul> xwidhlv ytbvvmyxyftfxc gtxh c tqdawuv e y nvk igl r hvdtr vdvur ilgndutam simmer <p><big><font color=3D"#000080"><strong><b>Do </b><alligator><b>This Al= </b><awake><b>l Wi</b><confectionery><b>th:</strong> </font></big> <ul> <li><font face=3D"V...

...ot * R-R.rsp * R-Rsamtools * R-rsconnect * R-Rsolid * R-RSQLite * R-rstudioapi * R-rsvg * R-rtracklayer * R-RUnit * R-R.utils * R-rversions * R-rvest * R-S4Vectors * R-sandwich * R-scales * R-scatterplot3d * R-sciplot * R-selectr * R-sessioninfo * R-sfsmisc * R-shiny * R-showtext * R-showtextdb * R-simmer * R-snow * R-sodium * R-sourcetools * R-sp * R-spelling * R-statmod * R-statnet.common * R-stringdist * R-stringi * R-stringr * R-styler * R-SummarizedExperiment * R-svglite * R-sys * R-sysfonts * R-systemfit * R-testit * R-testthat * R-tibble * R-tidyr * R-tidyselect * R-tikzDevice * R-timeDate *...

Hi, documentation is always good and this is a great idea. It'll be particularly useful as a place where additional examples of constructs from non-C-family languages could be added (since most compiler tutorials inevitably focus on languages that are a lot like C/C++/Obj-C). I'd imagine you've already thought of this, but it might be something where using pseudo-LLVM-IR is of the