|
If you were logged in you would be able to see more operations.
|
|
|
|
Time Tracking:
|
|
Original Estimate:
|
2h
|
|
|
Remaining Estimate:
|
2h
|
|
|
Time Spent:
|
Not Specified
|
|
|
|
| Severity: |
Incorrect Behavior
|
|
The LIMITS.cpp config test tries to determine exact-width integer typese (the equivalent of things such as int32_t) but it fails to consider the fact that all integer types other than unsigned char may have padding bits that contribute to their size but not to their range (i.e., there may be two or more distinct bit patters that represent the same value, or bit patterns that do not correspond to any value at all). This is only an issue in theory since we know of no architecture with such a representation.
|
|
Description
|
The LIMITS.cpp config test tries to determine exact-width integer typese (the equivalent of things such as int32_t) but it fails to consider the fact that all integer types other than unsigned char may have padding bits that contribute to their size but not to their range (i.e., there may be two or more distinct bit patters that represent the same value, or bit patterns that do not correspond to any value at all). This is only an issue in theory since we know of no architecture with such a representation. |
Show » |
|
on comp.lang.c
Bug
Open
Trivial
LIMITS.cpp assumes integers with no padding bits
