diff options
author | Simon Peyton Jones <simonpj@microsoft.com> | 2015-06-26 11:40:01 +0100 |
---|---|---|
committer | Simon Peyton Jones <simonpj@microsoft.com> | 2015-06-26 17:53:22 +0100 |
commit | 0696fc6d4de28cb589f6c751b8491911a5baf774 (patch) | |
tree | af20b546dbd408fba284cadeeded66f089d11fb7 /testsuite/tests/stranal/should_compile/T10482a.hs | |
parent | caf9d427d423a8ff63fd4c5a1332d058004751ff (diff) | |
download | haskell-0696fc6d4de28cb589f6c751b8491911a5baf774.tar.gz |
Improve CPR behavior for strict constructors
When working on Trac #10482 I noticed that we could give constructor
arguments the CPR property if they are use strictly.
This is documented carefully in
Note [CPR in a product case alternative]
and also
Note [Initial CPR for strict binders]
There are a bunch of intersting examples in
Note [CPR examples]
which I have added to the test suite as T10482a.
I also added a test for #10482 itself.
Diffstat (limited to 'testsuite/tests/stranal/should_compile/T10482a.hs')
-rw-r--r-- | testsuite/tests/stranal/should_compile/T10482a.hs | 63 |
1 files changed, 63 insertions, 0 deletions
diff --git a/testsuite/tests/stranal/should_compile/T10482a.hs b/testsuite/tests/stranal/should_compile/T10482a.hs new file mode 100644 index 0000000000..e633ebe6b7 --- /dev/null +++ b/testsuite/tests/stranal/should_compile/T10482a.hs @@ -0,0 +1,63 @@ +{-# LANGUAGE TypeFamilies #-} +{-# OPTIONS_GHC -fno-unbox-small-strict-fields #-} + -- Makes f2 a bit more challenging + +-- Tests inspired by Note [CPR examples] in DmdAnal, and Trac #10482 + +module Foo where + + +h :: Int -> Int -> Bool +h 0 y = y>0 +h n y = h (n-1) y + +-- The main point: all of these functions can have the CPR property + +------- f1 ----------- +-- x is used strictly by h, so it'll be available +-- unboxed before it is returned in the True branch + +f1 :: Int -> Int +f1 x = case h x x of + True -> x + False -> f1 (x-1) + + +------- f2 ----------- +-- x is a strict field of MkT2, so we'll pass it unboxed +-- to $wf2, so it's available unboxed. This depends on +-- the case expression analysing (a subcomponent of) one +-- of the original arguments to the function, so it's +-- a bit more delicate. + +data T2 = MkT2 !Int Int + +f2 :: T2 -> Int +f2 (MkT2 x y) | y>0 = f2 (MkT2 x (y-1)) + | y>1 = 1 + | otherwise = x + + +------- f3 ----------- +-- h is strict in x, so x will be unboxed before it +-- is rerturned in the otherwise case. + +data T3 = MkT3 Int Int + +f3 :: T3 -> Int +f3 (MkT3 x y) | h x y = f3 (MkT3 x (y-1)) + | otherwise = x + + +------- f4 ----------- +-- Just like f2, but MkT4 can't unbox its strict +-- argument automatically, as f2 can + +data family Foo a +newtype instance Foo Int = Foo Int + +data T4 a = MkT4 !(Foo a) Int + +f4 :: T4 Int -> Int +f4 (MkT4 x@(Foo v) y) | y>0 = f4 (MkT4 x (y-1)) + | otherwise = v |