Hi Alexey, >> Is there anything obvious I am missing that might affect the >> performance between 3.5 and 3.6? Like is something enabled that used >> to be disabled or missing? >> >> Otherwise, below is what a typical compiler invocation looks like. In >> the past, it performed fine. Does it set off any red flags for anyone? >> >> For completeness, I'm trying to run self tests under the sanitizers. >> I'm interested in the dynamic analysis at this point, and not static >> analysis provided by ccc-analyze and friends. > > Interesting. Could you share the performance numbers, and try to figure out > which specific sanitizer > is causing a problem (i.e. try to compare just -fsanitize=address, and then > various flavors of -fsanitize=undefined > one by one: -fsanitize=shift, -fsanitize=null etc.). We are not aware of > known performance degradation under > sanitizers in 3.6 release.
Yes, will do. I should have the performance data between 3.5 and 3.6 later tonight. I blew out my Clang 3.5 install, so I need to fetch it and build it again. Jeff _______________________________________________ cfe-users mailing list cfe-users@cs.uiuc.edu http://lists.cs.uiuc.edu/mailman/listinfo/cfe-users
