forked from mpaland/printf
-
Notifications
You must be signed in to change notification settings - Fork 52
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
GCC Conversion Warnings #105
Labels
resolved-on-develop
A changeset fixing this issue has been commiutted to the development branch
task
Comments
(This is on develop) |
eyalroz
added a commit
that referenced
this issue
Jan 25, 2022
…t, and some additional minor changes: * Now compiling with the `-Wconversion` warning flag when using clang or gcc. * In all cases noticed by gcc in which an implicit conversion was made which could change the converted value - have changed the conversion to be explicit. * Renamed: `get_sign()` -> `get_sign_bit()` (so as to clarify the return value is either 0 or 1, not -1 or 1). * Added explanatory comment for the `double_components` structure.
Fixed this, and added |
eyalroz
added
task
resolved-on-develop
A changeset fixing this issue has been commiutted to the development branch
labels
Jan 25, 2022
Thanks! |
eyalroz
added a commit
that referenced
this issue
Jan 26, 2022
…t, and some additional minor changes: * Now compiling with the `-Wconversion` warning flag when using clang or gcc. * In all cases noticed by gcc in which an implicit conversion was made which could change the converted value - have changed the conversion to be explicit. * Renamed: `get_sign()` -> `get_sign_bit()` (so as to clarify the return value is either 0 or 1, not -1 or 1). * Added explanatory comment for the `double_components` structure.
eyalroz
added a commit
that referenced
this issue
Jan 26, 2022
…t, and some additional minor changes: * Now compiling with the `-Wconversion` warning flag when using clang or gcc. * In all cases noticed by gcc in which an implicit conversion was made which could change the converted value - have changed the conversion to be explicit. * Renamed: `get_sign()` -> `get_sign_bit()` (so as to clarify the return value is either 0 or 1, not -1 or 1). * Added explanatory comment for the `double_components` structure.
eyalroz
added a commit
that referenced
this issue
Jan 31, 2022
…t, and some additional minor changes: * Now compiling with the `-Wconversion` warning flag when using clang or gcc. * In all cases noticed by gcc in which an implicit conversion was made which could change the converted value - have changed the conversion to be explicit. * Renamed: `get_sign()` -> `get_sign_bit()` (so as to clarify the return value is either 0 or 1, not -1 or 1). * Added explanatory comment for the `double_components` structure.
eyalroz
added a commit
that referenced
this issue
Jan 31, 2022
…t, and some additional minor changes: * Now compiling with the `-Wconversion` warning flag when using clang or gcc. * In all cases noticed by gcc in which an implicit conversion was made which could change the converted value - have changed the conversion to be explicit. * Renamed: `get_sign()` -> `get_sign_bit()` (so as to clarify the return value is either 0 or 1, not -1 or 1). * Added explanatory comment for the `double_components` structure.
eyalroz
added a commit
that referenced
this issue
Jan 31, 2022
…t, and some additional minor changes: * Now compiling with the `-Wconversion` warning flag when using clang or gcc. * In all cases noticed by gcc in which an implicit conversion was made which could change the converted value - have changed the conversion to be explicit. * Renamed: `get_sign()` -> `get_sign_bit()` (so as to clarify the return value is either 0 or 1, not -1 or 1). * Added explanatory comment for the `double_components` structure.
eyalroz
added a commit
that referenced
this issue
Feb 7, 2022
…t, and some additional minor changes: * Now compiling with the `-Wconversion` warning flag when using clang or gcc. * In all cases noticed by gcc in which an implicit conversion was made which could change the converted value - have changed the conversion to be explicit. * Renamed: `get_sign()` -> `get_sign_bit()` (so as to clarify the return value is either 0 or 1, not -1 or 1). * Added explanatory comment for the `double_components` structure.
eyalroz
added a commit
that referenced
this issue
Feb 10, 2022
…t, and some additional minor changes: * Now compiling with the `-Wconversion` warning flag when using clang or gcc. * In all cases noticed by gcc in which an implicit conversion was made which could change the converted value - have changed the conversion to be explicit. * Renamed: `get_sign()` -> `get_sign_bit()` (so as to clarify the return value is either 0 or 1, not -1 or 1). * Added explanatory comment for the `double_components` structure.
eyalroz
added a commit
that referenced
this issue
Feb 11, 2022
…t, and some additional minor changes: * Now compiling with the `-Wconversion` warning flag when using clang or gcc. * In all cases noticed by gcc in which an implicit conversion was made which could change the converted value - have changed the conversion to be explicit. * Renamed: `get_sign()` -> `get_sign_bit()` (so as to clarify the return value is either 0 or 1, not -1 or 1). * Added explanatory comment for the `double_components` structure.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
resolved-on-develop
A changeset fixing this issue has been commiutted to the development branch
task
GCC with -Wconversion highlights conversions that may change values.
I can resolve these in a PR with the proper casts, but I wanted you to take a look first in case you think some of them should be resolved through other means.
The text was updated successfully, but these errors were encountered: