Now the pass is just a tiny wrapper around the util. This lets us reuse the logic elsewhere (done here for BuildLibCalls) instead of duplicating it.
I put it in BuildLibCalls.h. I think the next step is to have something like getOrInsertLibFunc that also sets the attributes.
I tried having this in TLI itself, but that doesn't feel right for an analysis. I also tried having the analysis return an AttributeSet that users would then apply; I think that's still a little awkward though. Thoughts?
Looks like we could refactor all of these under something like TLI::get(M, "strchr")?