simon_tatham added a comment. No, I haven't measured it. Partly because that was one of the (many) things I was going to leave until after I //didn't// get feedback on the first draft that discouraged me from the whole idea :-) and also because I've already thought of one thing I can do to speed it up that I haven't done yet.
(Namely, break the pathname down recursively from the RH end instead of iteratively from the LH, so that in the case where the whole pathname is already case-correct, the lookup can succeed immediately. Then any performance hit should be limited to //only// the cases that actually need fixing up.) I can see that if you're on Linux specifically then a FUSE filesystem can solve the case insensitivity, albeit in a way that needs setup and teardown. But surely backslash path separators are still problematic in that situation? (Or does ciopfs have an option I didn't spot to fudge those too?) Repository: rC Clang https://reviews.llvm.org/D48626 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
