similar to: Building GC on statepoint-example

Jordon, I just submitted a change to the docs to hopefully address your confusion.  Can you take a look and let me know if you have further questions?  Start with the revised Stack Map Format section. Philip p.s. I just submitted this and it'll take a few minutes to refresh.  In the meantime, you could look at the diff for 346405. On 11/2/18 2:52 PM, Jordan Rudd via llvm-dev wrote:

Dear All I need to read the stackmap section at runtime of the inspected application. I've read the documentation of stackmap and found this paragraph: "A JIT compiler can easily access this section by providing its own memory manager via the LLVM C API LLVMCreateSimpleMCJITMemoryManager(). When creating the memory manager, the JIT provides a callback:

Philip Reames wrote: > Any change outside of statepoint lowering is highly suspect. Notice that SelectionDAGBuilder::LowerCallTo (the one I'm modifying) has exactly one other caller: visitCall, which doesn't match vararg functions. Every other codepath directly calls TargetLowering::LowerCallTo, supplying CallLoweringInfo information explicity (it's a structure with a vararg

Buenas, Tengo un problema y es que intentando conectarme a una base de datos SQL Server, tras cosneguirme conectarme usando el paquete odbc, me deja acceder al contenido de algunas tablas (mediante un select), pero sin embargo en otras me pone lo siguiente: Error in new_result(connection en ptr, statement) : std::bad_alloc No entiendo muy bien porque me salta ese error, ya que desde SQL si

Perdon, corrijo, es justo eso... En cuanto hay uan cadena de tipo varchar falla. Es por temas de codificaciones en el driver. ?Como cambio la codificacion? Un saludo Jesus ________________________________ De: David Luna <ofc587a87 en gmail.com> Enviado: viernes, 2 de marzo de 2018 15:02 Para: Jes?s Para Fern?ndez Cc: r-help-es en r-project.org Asunto: Re: [R-es] Problemas de conexion con

Hi, I am looking to utilize LLVM as the backend in an existing compiler for a garbage collected language, and have a question regarding the current and future support for precise GC in LLVM. It appears that gc.root is being phased out, with with breaking changes such as this: http://reviews.llvm.org/D7004 <http://reviews.llvm.org/D7004> Does this mean that gc.statepoint is ready for

Buenas El problema es el tipo dr columnas. Haynun bug q hace que haya q mostrar el tipo de columna mas largo al final de la consulta... Es un bug de los odbc de Windows.. Gracias Jes?s Obtener Outlook para Android<https://aka.ms/ghei36> ________________________________ From: Javier Marcuzzi <javier.ruben.marcuzzi en gmail.com> Sent: Saturday, March 3, 2018 12:02:10 AM To: Jes?s

Hi, I'm trying to use the statepoint-example strategy to build a simple garbage collector. After using the PlaceSafepoints and RewriteStatepointsForGC passes, I can successfully generate a stack map in my binary and call into my runtime's gc poll. As far as I can tell, I need the stack pointer at the point of the poll to find the correct frame in the stack map. I'm having trouble

Hello, list I am not quite sure if what I'm experiencing is a bug or intentional behavior. In the code below the result of a function call is a deopt arg to llvm.experimental.gc.statepoint (http://llvm.org/docs/Statepoints.html#llvm-experimental-gc-statepoint-intrinsic). Therefore a Stack Map containing location of this variable is created upon code generation. Here's the complete

Hi, Sanjoy, On 2015-11-16 23:27, Sanjoy Das wrote: > Hi Vlad, > > vlad via llvm-dev wrote: >>> Vlad, >>> >>> My initial impression is that you've stumbled across a bug. I suspect >>> that we - the only active users of the deopt info in the statepoint I >>> know of - have been inverting the meaning of Direct and Indirect >>>

> Vlad, > > My initial impression is that you've stumbled across a bug. I suspect > that we - the only active users of the deopt info in the statepoint I > know of - have been inverting the meaning of Direct and Indirect > throughout our code. (i.e. we're consistent, but swapped on the > documented meaning) I've asked Sanjoy to confirm that, and if he >

I actually need this feature quite badly in my untyped language compiler: since I support first-class functions, I've made the types of all functions a standard vararg (so I can box them). The implementation crashes when I try to read out the value of gc.result. Hints as to what might be wrong? Signed-off-by: Ramkumar Ramachandra <artagnon at gmail.com> ---

Sorry, what does "PC" mean here? ________________________________ From: Philip Reames <listmail at philipreames.com> Sent: Thursday, November 8, 2018 7:27 AM To: Jordan Rudd; llvm-dev at lists.llvm.org Subject: Re: [llvm-dev] Passing stack pointer to statepoint-gc Jordon, First of all, StackMaps are keyed by PC, not by SP. Each entry corresponds to given location within the

No , lo mete como string... Obtener Outlook para Android<https://aka.ms/ghei36> ________________________________ From: Javier Marcuzzi <javier.ruben.marcuzzi en gmail.com> Sent: Friday, March 9, 2018 3:47:46 AM To: Jes?s Para Fern?ndez Cc: Lista R Subject: Re: [R-es] Imputar NA a SQL Server Estimado Jes?s Para Fern?ndez Pruebe lo siguiente: str_replace_all(values,

Buenas, Quiero meter NULL en algunos valores al hacer un insert en una base ded datos SQL Server, pero no me reconoce NA, por lo que no se como meterlos... ?Alguno sabe como podria hacerse? La opci?n de no meter el valor no es v?lida porque tengo que meter varias columans y los NA se pueden dar en cualqueira de ellas... Gracias Jes?s [[alternative HTML version deleted]]

I've been looking at inlining invokes / calls done through statepoints and I want to have a design discussion before I sink too much time into something I'll have to throw away. I'm not actively working on adding inlining support to patchpoints, but I suspect these issues are applicable towards teaching LLVM to inline through patchpoints as well. There are two distinct problems to

Specifically, I wanted to sit down with Sanjoy and Philip who have been working on getting the current statepoint infrastructure sufficiently well integrated with the optimizer to do early statepoint insertion, and discuss what the path forward is here. If anyone happens to be in the area and is interested in attending, please let me know. Currently, I'm planning to host things up on

The long term plan is a) evolving, and b) dependent on the specific use case. :) It would definitely be nice if we could support both early and late safepoint insertion. I see no reason that LLVM as a project should pick one or the other since the infrastructure required is largely overlapping. (Obviously, I'm going to be mostly working on the parts that I need, but others are always

Hi Chandler, A few of us up here in Seattle would be interested, but we’re too cheap to buy plane tickets. Is it reasonable to set up a conference call? How the optimizer deals with statepoints is important to us. -R From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Chandler Carruth Sent: Tuesday, July 28, 2015 8:21 PM To: Sanjoy Das <sanjoy at

Hi, My collector supports only base pointers as stack roots. This wasn't a problem until I tried to run some optimizations before RS4GC, which introduced (interior) derived pointers. The statepoint documentation mentions that these collectors exist, but doesn't mention whether and how this is currently supported. What could I do to make it work? -Manuel