Cabal revisions of ghc-events-analyze-0.2.8
Hackage metadata revisions edit the .cabal file after upload; each diff below is one revision.
revision 1
-name: ghc-events-analyze-version: 0.2.8-synopsis: Analyze and visualize event logs-description: ghc-events-analyze is a simple Haskell profiling tool that- uses GHC's eventlog system. It helps with some profiling- use cases that are not covered by the existing GHC- profiling modes or tools. It has two major features:- .- 1. While ThreadScope shows CPU activity across all your- cores, ghc-events-analyze shows CPU activity across all- your Haskell threads.- .- 2. It lets you label periods of time during program- execution (by instrumenting your code with special trace- calls) and then lets you visualize those time periods or- get statistics on them.- .- It is very useful for profiling code when ghc's normal- profiling mode is not available, or when using profiling- mode would perturb the code too much. It is also useful- when you want time-profiling information with a breakdown- over time rather than totals for the whole run.- .- The blog post- <http://www.well-typed.com/blog/2014/02/ghc-events-analyze/ Performance profiling with ghc-events-analyze>- describes the motivation in more detail.-license: BSD3-license-file: LICENSE-author: Edsko de Vries, Duncan Coutts, Mikolaj Konarski-maintainer: edsko@well-typed.com-copyright: 2013-2014 Well-Typed LLP-category: Development, Profiling, Trace-build-type: Simple-extra-source-files: ChangeLog-cabal-version: >=1.10--source-repository head- type: git- location: https://github.com/edsko/ghc-events-analyze--executable ghc-events-analyze- main-is: GHC/RTS/Events/Analyze.hs- other-modules: GHC.RTS.Events.Analyze.Analysis- GHC.RTS.Events.Analyze.Options- GHC.RTS.Events.Analyze.StrictState- GHC.RTS.Events.Analyze.Utils- GHC.RTS.Events.Analyze.Types- GHC.RTS.Events.Analyze.Script- GHC.RTS.Events.Analyze.Script.Standard- GHC.RTS.Events.Analyze.Reports.Totals- GHC.RTS.Events.Analyze.Reports.Timed- GHC.RTS.Events.Analyze.Reports.Timed.SVG-- build-depends: base >= 4.9 && < 4.15,- blaze-svg >= 0.3 && < 0.4,- bytestring >= 0.10 && < 0.12,- containers >= 0.5 && < 0.7,- diagrams-lib >= 1.3 && < 1.5,- diagrams-svg >= 1.1 && < 1.5,- filepath >= 1.3 && < 1.5,- ghc-events >= 0.13 && < 0.14,- hashable >= 1.2 && < 1.4,- lens >= 3.10 && < 4.20,- mtl >= 2.2.1 && < 2.3,- optparse-applicative >= 0.11 && < 0.17,- parsec >= 3.1 && < 3.2,- regex-base >= 0.93 && < 0.95,- regex-pcre-builtin >= 0.94 && < 0.96,- SVGFonts >= 1.7 && < 1.8,- text < 1.3,- th-lift >= 0.6 && < 0.9,- th-lift-instances >= 0.1 && < 0.2,- transformers >= 0.3 && < 0.6,- unordered-containers >= 0.2 && < 0.3,- -- No version: whatever is bundled with ghc- template-haskell-- hs-source-dirs: src- default-language: Haskell2010- ghc-options: -Wall -rtsopts-- default-extensions: NamedFieldPuns- RecordWildCards- NoMonomorphismRestriction- ScopedTypeVariables- ViewPatterns- BangPatterns- RankNTypes- MultiParamTypeClasses- other-extensions: CPP- TemplateHaskell+name: ghc-events-analyze +version: 0.2.8 +synopsis: Analyze and visualize event logs +description: ghc-events-analyze is a simple Haskell profiling tool that + uses GHC's eventlog system. It helps with some profiling + use cases that are not covered by the existing GHC + profiling modes or tools. It has two major features: + . + 1. While ThreadScope shows CPU activity across all your + cores, ghc-events-analyze shows CPU activity across all + your Haskell threads. + . + 2. It lets you label periods of time during program + execution (by instrumenting your code with special trace + calls) and then lets you visualize those time periods or + get statistics on them. + . + It is very useful for profiling code when ghc's normal + profiling mode is not available, or when using profiling + mode would perturb the code too much. It is also useful + when you want time-profiling information with a breakdown + over time rather than totals for the whole run. + . + The blog post + <http://www.well-typed.com/blog/2014/02/ghc-events-analyze/ Performance profiling with ghc-events-analyze> + describes the motivation in more detail. +license: BSD3 +license-file: LICENSE +author: Edsko de Vries, Duncan Coutts, Mikolaj Konarski +maintainer: edsko@well-typed.com +copyright: 2013-2014 Well-Typed LLP +category: Development, Profiling, Trace +build-type: Simple +extra-source-files: ChangeLog +cabal-version: >=1.10 +x-revision: 1 + +source-repository head + type: git + location: https://github.com/edsko/ghc-events-analyze + +executable ghc-events-analyze + main-is: GHC/RTS/Events/Analyze.hs + other-modules: GHC.RTS.Events.Analyze.Analysis + GHC.RTS.Events.Analyze.Options + GHC.RTS.Events.Analyze.StrictState + GHC.RTS.Events.Analyze.Utils + GHC.RTS.Events.Analyze.Types + GHC.RTS.Events.Analyze.Script + GHC.RTS.Events.Analyze.Script.Standard + GHC.RTS.Events.Analyze.Reports.Totals + GHC.RTS.Events.Analyze.Reports.Timed + GHC.RTS.Events.Analyze.Reports.Timed.SVG + + build-depends: base >= 4.9 && < 4.19, + blaze-svg >= 0.3 && < 0.4, + bytestring >= 0.10 && < 0.12, + containers >= 0.5 && < 0.7, + diagrams-lib >= 1.3 && < 1.5, + diagrams-svg >= 1.1 && < 1.5, + filepath >= 1.3 && < 1.5, + ghc-events >= 0.13 && < 0.20, + hashable >= 1.2 && < 1.5, + lens >= 3.10 && < 6.0, + mtl >= 2.2.1 && < 2.4, + optparse-applicative >= 0.11 && < 0.18, + parsec >= 3.1 && < 3.2, + regex-base >= 0.93 && < 0.95, + regex-pcre-builtin >= 0.94 && < 0.96, + -- SVGFonts 1.8 introduces breaking changes, we'll need to change some code + SVGFonts >= 1.7 && < 1.8, + text < 1.3 || >= 2 && < 2.1, + th-lift >= 0.6 && < 0.9, + th-lift-instances >= 0.1 && < 0.2, + transformers >= 0.3 && < 0.7, + unordered-containers >= 0.2 && < 0.3, + -- No version: whatever is bundled with ghc + template-haskell + + hs-source-dirs: src + default-language: Haskell2010 + ghc-options: -Wall -rtsopts + + default-extensions: NamedFieldPuns + RecordWildCards + NoMonomorphismRestriction + ScopedTypeVariables + ViewPatterns + BangPatterns + RankNTypes + MultiParamTypeClasses + other-extensions: CPP + TemplateHaskell QuasiQuotes