You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stdcxx.apache.org by "Martin Sebor (JIRA)" <ji...@apache.org> on 2007/08/23 06:00:38 UTC
[jira] Updated: (STDCXX-423) LIMITS.cpp assumes integers with no
padding bits
[ https://issues.apache.org/jira/browse/STDCXX-423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Sebor updated STDCXX-423:
--------------------------------
Fix Version/s: 4.2.1
Scheduled for sometime after 4.2.
> LIMITS.cpp assumes integers with no padding bits
> ------------------------------------------------
>
> Key: STDCXX-423
> URL: https://issues.apache.org/jira/browse/STDCXX-423
> Project: C++ Standard Library
> Issue Type: Bug
> Components: Configuration
> Affects Versions: 4.1.2, 4.1.3, 4.2
> Environment: unknown
> Reporter: Martin Sebor
> Priority: Trivial
> Fix For: 4.2.1
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.