Thanks for the update! Some additional questions: - Why does scan-build-py need to distinguish between "installed" and "non-installed mode"? And, in particular, does using the dynamic linker preload technique require installation? It seems to me that it shouldn't.
- Can we just remove "installed mode"? What benefit does it provide? If the only benefit is speed, do you think the speed is worth the extra complexity? - Does your latest update call the existing perl ccc-analyzer script? I see you have added python-based "intercept-cc" and "intercept-cxx". Can scan-build-py be changed to call the existing ccc-analyzer rather than doing its own wrapping? The goal of deferring to ccc-analyzer is to make sure that we preserve the existing behavior of scan-build. http://reviews.llvm.org/D9600 EMAIL PREFERENCES http://reviews.llvm.org/settings/panel/emailpreferences/ _______________________________________________ cfe-commits mailing list cfe-commits@cs.uiuc.edu http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
