#14242: Ticks and join points don't play well -------------------------------------+------------------------------------- Reporter: bgamari | Owner: (none) Type: bug | Status: patch Priority: normal | Milestone: 8.4.1 Component: Compiler | Version: 8.2.1 Resolution: | Keywords: Operating System: Unknown/Multiple | Architecture: | Unknown/Multiple Type of failure: None/Unknown | Test Case: Blocked By: | Blocking: Related Tickets: | Differential Rev(s): Wiki Page: | -------------------------------------+------------------------------------- Comment (by Ben Gamari <ben@…>): In [changeset:"12a92fedf8b1997f2e26800929be117d54536b7e/ghc" 12a92fed/ghc]: {{{ #!CommitTicketReference repository="ghc" revision="12a92fedf8b1997f2e26800929be117d54536b7e" OccurAnal: Ensure SourceNotes don't interfere with join-point analysis In general ticks are problematic for join point analysis as described in #14242. However, source notes are intended to be a best-effort annotation which shouldn't interfere with optimization. Special-case these to ensure that tail-call information is still correct, even in the presence of source note ticks. Test Plan: Validate Reviewers: simonpj, austin Reviewed By: simonpj Subscribers: rwbarton, thomie GHC Trac Issues: #14242 Differential Revision: https://phabricator.haskell.org/D3978 }}} -- Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/14242#comment:2> GHC <http://www.haskell.org/ghc/> The Glasgow Haskell Compiler