RE: Can we mark DataCon ptrs only in allocation sites and not generate entry code?

2016-08-25 Thread Simon Peyton Jones via ghc-devs
s part of the return protocol for returning from a constructor. Simon -Original Message- From: Ömer Sinan Ağacan [mailto:omeraga...@gmail.com] Sent: 25 August 2016 17:46 To: Simon Peyton Jones Cc: ghc-devs Subject: Re: Can we mark DataCon ptrs only in allocation sites and not

Re: Can we mark DataCon ptrs only in allocation sites and not generate entry code?

2016-08-25 Thread Ömer Sinan Ağacan
age- > | From: ghc-devs [mailto:ghc-devs-boun...@haskell.org] On Behalf Of Ömer > | Sinan Agacan > | Sent: 25 August 2016 11:46 > | To: ghc-devs > | Subject: Can we mark DataCon ptrs only in allocation sites and not > | generate entry code? > | > | As far as I ca

RE: Can we mark DataCon ptrs only in allocation sites and not generate entry code?

2016-08-25 Thread Simon Peyton Jones via ghc-devs
mmCon case. But also we clearly must do so in the entry code for a data constructor Simon | -Original Message- | From: ghc-devs [mailto:ghc-devs-boun...@haskell.org] On Behalf Of Ömer | Sinan Agacan | Sent: 25 August 2016 11:46 | To: ghc-devs | Subject: Can we mark DataCon pt

Can we mark DataCon ptrs only in allocation sites and not generate entry code?

2016-08-25 Thread Ömer Sinan Ağacan
As far as I can see in the native code compiler we mark DataCon pointers in two places: 1. In allocation sites (StgCmmCon.hs:240) 2. In DataCon entry code (StgCmm.hs:244) I was wondering why we can't get away with just doing (1). Can anyone give me an example where an allocation doesn't return a