search for: com&data

Buenas, Alguno ha probado a usar Microsfot R Open? Segun leo, se han centrado en hacer que R por defecto sea multicore (cosa que podemos hacer usando parallel, foreach...) https://mran.revolutionanalytics.com/documents/rro/multithread Home [mran.revolutionanalytics.com]<https://mran.revolutionanalytics.com/documents/rro/multithread> This site uses cookies for analytics, personalized content and ads. By continuing to browse this site, you agree to this use. Learn more mran.revolutionanalytics.com...

De acuerdo Carlos pero en mi ordenador no funciona y me da el error que he comentado. Muchas gracias por tu colaboración. Saludos, Juan El 04/03/2018 a las 20:09, Carlos J. Gil Bellosta escribió: Corre perfectamente en mi máquina si borro la última línea (print(environment(show))). Simplemente, he creado un directorio vacío (/tmp/prueba), he copiado el código (menos esa...

Sorry to reply to myself here, but I had an idea regarding "issue #2" -- possibly what makes the most sense for those clients/targets is to pull the pointer difference computation/reapplication into RS4GC itself -- it could have a pass just before or after rematerialization, which runs based on a configuration flag (eventually to be driven by GCStrategy), which performs rewrites like below to ensure that only base pointers are live across statepoints when it's do...

...urrent mechanism for that lowering keys off the gc.relocate calls for generating the fills, and the gc.relocate calls wouldn't be present for the cases that need to be "VeryIndirect"... Thanks -Joseph -----Original Message----- From: Sanjoy Das [mailto:sanjoy at playingwithpointers.com] Sent: Friday, February 5, 2016 7:05 PM To: Joseph Tremoulet <jotrem at microsoft.com> Cc: Philip Reames <listmail at philipreames.com>; Manuel Jacob <me at manueljacob.de>; llvm-dev <llvm-dev at lists.llvm.org> Subject: Re: [llvm-dev] gc relocations on exception path w/RS4...

..., where TargetAddress is dereferenced inside of the COFF::IMAGE_REL_AMD64_ADDR64 case of resolveRelocation inside RuntimeDyldCOFFx86_64. I took a look at the link provided earlier and noticed a few things... - LLILC provides a resolver that simply returns UINT64_MAX for any given symbol, which the comment explains indicates means that we want to skip relocation resolution and that the client code will handle it manually. - recordRelocations is supposed to be that “manual handling” This raises the following questions: 1) Forgive the noobishness of this, but what is meant by “external” relocation...

...y, we have a design inconsistency where we expect to be able to "resume" a phi of arbitrary landing pads, but we expect relocations to be tied specifically to a particular invoke. Chen, Joseph, and I have spent some time talking about how to resolve this. All of the schemes we've come up with representing relocations using gc.relocates on the exceptional path require either a change to how we define an invoke instruction (something we'd really like to avoid) or a new intrinsic with special treatment in the optimizer so that it basically "becomes part of" the l...