On Jun 13, 2015 8:21 PM, "James Y Knight" <[email protected]> wrote: > > On Jun 13, 2015, at 1:23 PM, Rafael Espindola <[email protected]> wrote: >> >> And on some libstdc++ those virtual functions conclude that >> >> ------------------------ >> int main() { >> std::error_code foo = std::make_error_code(std::errc::no_such_file_or_directory); >> return foo == std::errc::no_such_file_or_directory; >> } >> ------------------------- >> >> should exit with 0. > > > This is GCC "RESOLVED INVALID" https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66438 >
Thanks. In general it looks like we can't guarantee that a llvm built with gcc 4.9 will work in a system with 5.0 installed. In the particular case of std::errc, using it in llvm should be considered a bug in the same way that using iostream is. Cheers, Rafael
_______________________________________________ cfe-commits mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
