r239684 - Don't use std::errc.

Rafael EspĂ­ndola rafael.espindola at gmail.com
Sun Jun 14 06:08:14 PDT 2015


On Jun 13, 2015 8:21 PM, "James Y Knight" <jyknight at google.com> wrote:
>
> On Jun 13, 2015, at 1:23 PM, Rafael Espindola <rafael.espindola at gmail.com>
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-commits/attachments/20150614/964e30a3/attachment.html>


More information about the cfe-commits mailing list