-
Notifications
You must be signed in to change notification settings - Fork 130
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New GCC 5.0 hits problem with narrowing in list-initializers #26
Labels
Comments
Reported by |
Reported by |
jmhodges
added a commit
to jmhodges/cld2
that referenced
this issue
Oct 23, 2016
Use a bunch of static_cast<uint8> to get around the c++11-narrowing errors when building as C++0x. This hack is necessary because the source files and generation code has not been released. See CLD2Owners#33 on the source file check-in. See CLD2Owners#47 CLD2Owners#51 CLD2Owners#26 and I'm sure there are others for the C++0x problem.
This was referenced Oct 23, 2016
jmhodges
added a commit
to jmhodges/cld2
that referenced
this issue
Oct 23, 2016
hack up generated files to compile as c++0x Use a bunch of static_cast<uint8> to get around the c++11-narrowing errors when building as C++0x. This hack is necessary because the source files and generation code has not been released. See CLD2Owners#33 on the source file check-in. See CLD2Owners#47 CLD2Owners#51 CLD2Owners#26 and I'm sure there are others for the C++0x problem.
jjhoughton
pushed a commit
to jjhoughton/cld2
that referenced
this issue
Jul 9, 2022
Use a bunch of static_cast<uint8> to get around the c++11-narrowing errors when building as C++0x. This hack is necessary because the source files and generation code has not been released. See CLD2Owners#33 on the source file check-in. See CLD2Owners#47 CLD2Owners#51 CLD2Owners#26 and I'm sure there are others for the C++0x problem.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Originally reported on Google Code with ID 26
Reported by
marxin.liska
on 2015-01-05 10:34:02The text was updated successfully, but these errors were encountered: