>>> Trying... >>> No, that doesn't work either. Same valgrind warnings too. >>> Should I revert llvm to r42817 too? >> >> I just committed a patch that should fix the valgrind errors below, >> please try it out. If there are still valgrind warnings, please let >> me know, thanks! > > It still does: > > ==16236== Memcheck, a memory error detector. > ==16236== Copyright (C) 2002-2007, and GNU GPL'd, by Julian Seward > et al. > ==16236== Using LibVEX rev 1732, a library for dynamic binary > translation. > ==16236== Copyright (C) 2004-2007, and GNU GPL'd, by OpenWorks LLP. > ==16236== Using valgrind-3.2.3-Debian, a dynamic binary > instrumentation framework. > ==16236== Copyright (C) 2000-2007, and GNU GPL'd, by Julian Seward > et al. > ==16236== For more details, rerun with: -v > ==16236== > ==16236== Conditional jump or move depends on uninitialised value(s) > ==16236== at 0x51B006: clang::IdentifierInfo::getPPKeywordID() > const (in /usr/local/bin/clang) > ==16236== by 0x514B24: > clang::Preprocessor::HandleDirective(clang::Token&) (in > /usr/local/bin/clang) > ==16236== by 0x503A2D: > clang::Lexer::LexTokenInternal(clang::Token&) (in > /usr/local/bin/clang)
Ok, very strange. As Anton mentioned, please try with a debug build. This should give us line numbers which will make it easier to identify the problem. -Chris _______________________________________________ cfe-dev mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev
