A way to compile Firefox with all unused code paths clipped from the build?

(Joe Pea) #1

Hello, I’m new to the forums. Is there some way to compile Firefox with only the features that I use?

For example, is it possible to somehow instrument all code paths, profile runtime usage based on a set of expected actions, then compile Firefox (or any program in general) with only the code paths that it ever touches?