#6084: Add stg_ap_pnnv and related call patterns
---------------------------------+------------------------------------------
Reporter: SimonMeier | Owner: simonmar
Type: feature request | Status: new
Priority: normal | Milestone: 7.8.1
Component: Runtime System | Version: 7.4.1
Keywords: | Os: Unknown/Multiple
Architecture: Unknown/Multiple | Failure: None/Unknown
Difficulty: Unknown | Testcase:
Blockedby: | Blocking:
Related: |
---------------------------------+------------------------------------------
Comment(by simonmar):
Replying to [comment:3 SimonMeier]:
> The change only improves unknown calls with unboxed arguments and a
final void argument. Attoparsec does not profit, as it does not require
side-effects. The binary builder could profit, but in its current form it
would additipnally require the stg_ap_pnnnv and stg_ap_nnnv call patterns.
I don't understand why side-effects is an issue, and why you say that
Attoparsec would not benefit. Could you elaborate?
Also I don't understand why Builder would benefit, because the unknown
function in this case has type `(Buffer -> IO L.ByteString)`, which is
just the `stg_ap_pv` pattern, which we already have (it is a higher-order
function, so the `Buffer` argument won't be unboxed).
--
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/6084#comment:4>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler
_______________________________________________
Glasgow-haskell-bugs mailing list
Glasgow-haskell-bugs@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
