Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
cmd/compile: make deadcode pass cheaper and do it after cse #15306
[moved from discussion in CL 21981]
CSE can remove many values, so it'd be good to do a deadcode pass promptly after it, to speed up other passes. We used to, but it has slowly drifted away. However, deadcode allocates some potentially large slices: two work lists (small) and two bool slices (larger). We should make at least those bool slices reusable in f.Config and then add a deadcode after CSE.
Btw, @bradfitz, do you think it's worth having a label for compiler performance/speed (as opposed to compiled code performance)?