• <ins id="pjuwb"></ins>
    <blockquote id="pjuwb"><pre id="pjuwb"></pre></blockquote>
    <noscript id="pjuwb"></noscript>
          <sup id="pjuwb"><pre id="pjuwb"></pre></sup>
            <dd id="pjuwb"></dd>
            <abbr id="pjuwb"></abbr>

            chenglong7997

            Signed to unsigned conversion in C - is it always safe? (from stackoverflow)

            Suppose I have the following C code.

            unsigned int u = 1234;
            int i = -5678;

            unsigned int result = u + i;

            What implicit conversions are going on here, and is this code safe for all values of u and i? (Safe, in the sense that even though result in this example will overflow to some huge positive number, I could cast it back to an int and get the real result.)

            Answer:

            Short Answer

            Your i will be converted to an unsigned integer by adding UINT_MAX + 1, then the addition will be carried out with the unsigned values, resulting in a large result (depending on the values of u andi).

            Long Answer

            According to the C99 Standard:

            6.3.1.8 Usual arithmetic conversions

            1. If both operands have the same type, then no further conversion is needed.
            2. Otherwise, if both operands have signed integer types or both have unsigned integer types, the operand with the type of lesser integer conversion rank is converted to the type of the operand with greater rank.
            3. Otherwise, if the operand that has unsigned integer type has rank greater or equal to the rank of the type of the other operand, then the operand with signed integer type is converted to the type of the operand with unsigned integer type.
            4. Otherwise, if the type of the operand with signed integer type can represent all of the values of the type of the operand with unsigned integer type, then the operand with unsigned integer type is converted to the type of the operand with signed integer type.
            5. Otherwise, both operands are converted to the unsigned integer type corresponding to the type of the operand with signed integer type.

            In your case, we have one unsigned int (u) and signed int (i). Referring to (3) above, since both operands have the same rank, your i will need to be converted to an unsigned integer.

            6.3.1.3 Signed and unsigned integers

            1. When a value with integer type is converted to another integer type other than _Bool, if the value can be represented by the new type, it is unchanged.
            2. Otherwise, if the new type is unsigned, the value is converted by repeatedly adding or subtracting one more than the maximum value that can be represented in the new type until the value is in the range of the new type.
            3. Otherwise, the new type is signed and the value cannot be represented in it; either the result is implementation-defined or an implementation-defined signal is raised.

            Now we need to refer to (2) above. Your i will be converted to an unsigned value by adding UINT_MAX + 1. So the result will depend on how UINT_MAX is defined on your implementation. It will be large, but it will not overflow, because:

            6.2.5 (9)

            A computation involving unsigned operands can never overflow, because a result that cannot be represented by the resulting unsigned integer type is reduced modulo the number that is one greater than the largest value that can be represented by the resulting type.

            Bonus: Arithmetic Conversion Semi-WTF

            #include <stdio.h>

            int main(void)
            {
             
            unsigned int plus_one = 1;
             
            int minus_one = -1;

             
            if(plus_one < minus_one)
                printf
            ("1 < -1");
             
            else
                printf
            ("boring");

             
            return 0;
            }

            You can use this link to try this online: http://codepad.org/yPhYCMFO

            Bonus: Arithmetic Conversion Side Effect

            Arithmetic conversion rules can be used to get the value of UINT_MAX by initializing an unsigned value to -1, ie:

            unsigned int umax = -1; // umax set to UINT_MAX

            This is guaranteed to be portable regardless of the signed number representation of the system because of the conversion rules described above. See this SO question for more information: Is it safe to use -1 to set all bits to true?

            posted on 2012-08-17 02:32 Snape 閱讀(793) 評論(0)  編輯 收藏 引用 所屬分類: Traps

            導航

            <2025年6月>
            25262728293031
            1234567
            891011121314
            15161718192021
            22232425262728
            293012345

            統(tǒng)計

            常用鏈接

            留言簿

            隨筆分類

            隨筆檔案

            文章分類

            文章檔案

            my

            搜索

            最新評論

            閱讀排行榜

            評論排行榜

            精品久久久久久久国产潘金莲| 精品久久久久久无码专区不卡| 久久精品国产精品亚洲下载| 99热成人精品免费久久| 午夜精品久久久久久影视777| 国产精品久久久久a影院| 久久久久久久久无码精品亚洲日韩| 久久婷婷国产麻豆91天堂| 亚洲国产成人精品久久久国产成人一区二区三区综 | Xx性欧美肥妇精品久久久久久| 久久久久久A亚洲欧洲AV冫| 亚洲欧美成人综合久久久| 久久99精品久久久久久噜噜| 久久天堂AV综合合色蜜桃网 | 久久久老熟女一区二区三区| 国产精品久久久99| 99久久免费国产特黄| 国产成人无码精品久久久性色 | 久久99精品久久久久久噜噜| 国产V综合V亚洲欧美久久| 波多野结衣AV无码久久一区| 久久久久亚洲爆乳少妇无| 97精品国产91久久久久久| 久久久SS麻豆欧美国产日韩| 久久男人中文字幕资源站| 国产成人综合久久综合| 精品熟女少妇av免费久久| 亚洲综合伊人久久综合| 婷婷久久五月天| 伊人久久大香线蕉精品不卡| 久久久精品视频免费观看| 九九久久精品国产| 狠狠人妻久久久久久综合蜜桃 | 伊人久久无码精品中文字幕| 久久综合久久鬼色| 色99久久久久高潮综合影院| 韩国三级中文字幕hd久久精品| 久久av免费天堂小草播放| 亚洲国产精品成人久久蜜臀 | 亚洲国产精品无码久久SM| 蜜臀av性久久久久蜜臀aⅴ麻豆|