mozilla/rust — Issue #1938: add an LLVM-instruction profiler
Author: graydon
Created: 2012-03-06 23:09:28+00:00
State: open
Labels: A-codegen, A-llvm, I-slow

It seems one of our major bottlenecks remains simply the amount of code we're generating. Add a simple profiler for categorizing LLVM instructions (and the responsible party) as they're built. This may involve recreating the "builder" object we used to have (or some modern equivalent thereof, using typeclasses). Should sample based on a stack of named large-ish-grained translation contexts, so that the profile tells us something about responsible parties. Aim for 3-4 stack entries of context.