stdcxx-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Sebor (JIRA)" <j...@apache.org>
Subject [jira] Updated: (STDCXX-423) LIMITS.cpp assumes integers with no padding bits
Date Tue, 18 Mar 2008 17:51:24 GMT

     [ https://issues.apache.org/jira/browse/STDCXX-423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Martin Sebor updated STDCXX-423:
--------------------------------

              Severity: Incorrect Behavior
         Fix Version/s:     (was: 4.2.1)
                        4.3
    Remaining Estimate: 2h
     Original Estimate: 2h

Set Severity to Incorrect Behavior (in theory).
Set estimate.
Deferred until 4.3.

> 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.0
>         Environment: unknown
>            Reporter: Martin Sebor
>            Assignee: Martin Sebor
>            Priority: Trivial
>             Fix For: 4.3
>
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> 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.


Mime
View raw message