Due to a large amount of spam we do not allow new users to create repositories, they are "external" users. If you are a new user and want to create a repository, for example for forking GHC, open a new issue on ghc/ghc using the "get-verified" issue template
@@ -15,6 +15,7 @@ This part of the wiki collects all the information related to debugging GHC. Tha
...
@@ -15,6 +15,7 @@ This part of the wiki collects all the information related to debugging GHC. Tha
-[Debugging/ProfilingGhc](debugging/profiling-ghc): Profiling the compiler itself.
-[Debugging/ProfilingGhc](debugging/profiling-ghc): Profiling the compiler itself.
-[Debugging/TickyTicky](debugging/ticky-ticky): for debugging performance-related issues in compiled code. Typically for performance debugging of the Simplifier and Core-level optimisations.
-[Debugging/TickyTicky](debugging/ticky-ticky): for debugging performance-related issues in compiled code. Typically for performance debugging of the Simplifier and Core-level optimisations.
-[Debugging/CacheGrind](debugging/Cachegrind): Identify hot spots with instruction counts per line of GHC source code.
-[Debugging/LowLevelProfiling](debugging/low-level-profiling): way to investigate low-level performance, typically for performance debugging of the code generator or RTS.
-[Debugging/LowLevelProfiling](debugging/low-level-profiling): way to investigate low-level performance, typically for performance debugging of the code generator or RTS.
-[Debugging/CabalTest](debugging/cabal-test): the "`Cabal` test" for comparing performance of GHC builds
-[Debugging/CabalTest](debugging/cabal-test): the "`Cabal` test" for comparing performance of GHC builds
