search for: addrespace

...ult Motivation Managed language clients typically use address space 1 to represent GC-pointers. Some managed clients (CLR, in particular) allow construction of GC pointers to stack locations. For example, MSIL instruction ldloca (ECMA 335, p 370) creates a GC pointer to a stack local. Creating an addrespace(1)* pointer to a stack location currently involves two steps: the alloca, and an addrspacecast. Managed code transformations (ex: RewriteStatepointsForGC) do not handle arbitrary address space casting. So, it is desirable to obtain the addrespace(1)* pointer by construction. Thanks, Swaroop. -----...

...t   Motivation Managed language clients typically use address space 1 to represent GC-pointers. Some managed clients (CLR, in particular) allow construction of GC pointers to stack locations. For example, MSIL instruction ldloca (ECMA 335, p 370) creates a GC pointer to a stack local.   Creating an addrespace(1)* pointer to a stack location currently involves two steps: the alloca, and an addrspacecast. Managed code transformations (ex: RewriteStatepointsForGC) do not handle arbitrary address space casting. So, it is desirable to obtain the addrespace(1)* pointer by construction.   Thanks, Swaroop.

...ult Motivation Managed language clients typically use address space 1 to represent GC-pointers. Some managed clients (CLR, in particular) allow construction of GC pointers to stack locations. For example, MSIL instruction ldloca (ECMA 335, p 370) creates a GC pointer to a stack local. Creating an addrespace(1)* pointer to a stack location currently involves two steps: the alloca, and an addrspacecast. Managed code transformations (ex: RewriteStatepointsForGC) do not handle arbitrary address space casting. So, it is desirable to obtain the addrespace(1)* pointer by construction. I don't have a part...

...1 to > represent GC-pointers. > > Some managed clients (CLR, in particular) allow construction of GC > pointers to stack locations. > > For example, MSIL instruction ldloca (ECMA 335, p 370) creates a > GC pointer to a stack local. > > Creating an addrespace(1)* pointer to a stack location currently > involves two steps: the alloca, and an addrspacecast. > > Managed code transformations (ex: RewriteStatepointsForGC) do not > handle arbitrary address space casting. > > So, it is desirable to obtain the addrespace(1)* po...

...addresses are created as managed pointers. Which is why the proposal is to have alloca directly in the managed address-space seemed natural. Joseph has written more details in the document that Philip shared out in this thread. (2) A more Lower level IR view: LLVM creates all stack locations in addrespace(0) for all code, whether it comes from managed-code or native code. Of these, Stack locations corresponding to the managed-stack are promoted to managed-addresses via addrspacecast. As an optimization, the FrontEnd inserts the addrspace casts only for those stack locations that are actually addres...

...aged pointers. > Which is why the proposal is to have alloca directly in the managed address-space seemed natural. > > Joseph has written more details in the document that Philip shared out in this thread. > > (2) A more Lower level IR view: > LLVM creates all stack locations in addrespace(0) for all code, whether it comes from managed-code or native code. > Of these, Stack locations corresponding to the managed-stack are promoted to managed-addresses via addrspacecast. > As an optimization, the FrontEnd inserts the addrspace casts only for those stack locations that are actua...

Inline. From: Philip Reames [mailto:listmail at philipreames.com] Sent: Thursday, August 27, 2015 11:01 AM To: Swaroop Sridhar <Swaroop.Sridhar at microsoft.com>; llvm-dev <llvm-dev at lists.llvm.org>; Sanjoy Das <sanjoy at playingwithpointers.com> Cc: Joseph Tremoulet <jotrem at microsoft.com>; Andy Ayers <andya at microsoft.com>; Russell Hadley <rhadley at