• <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 閱讀(777) 評(píng)論(0)  編輯 收藏 引用 所屬分類: Traps

            導(dǎo)航

            <2012年6月>
            272829303112
            3456789
            10111213141516
            17181920212223
            24252627282930
            1234567

            統(tǒng)計(jì)

            常用鏈接

            留言簿

            隨筆分類

            隨筆檔案

            文章分類

            文章檔案

            my

            搜索

            最新評(píng)論

            閱讀排行榜

            評(píng)論排行榜

            亚洲精品第一综合99久久| 97久久精品人人做人人爽| 亚洲欧美伊人久久综合一区二区 | 欧美亚洲国产精品久久| 欧美黑人又粗又大久久久| 夜夜亚洲天天久久| av色综合久久天堂av色综合在| 国产成年无码久久久久毛片| 亚洲欧美成人久久综合中文网| 久久精品无码专区免费东京热| 国产呻吟久久久久久久92| 久久久久久久97| 久久99精品国产麻豆不卡| 久久亚洲中文字幕精品有坂深雪| 国产视频久久| 色综合久久中文综合网| 久久久av波多野一区二区| 亚洲欧美久久久久9999| 久久99精品国产麻豆蜜芽| 潮喷大喷水系列无码久久精品| 欧美亚洲国产精品久久| 久久影院久久香蕉国产线看观看| 国产精品久久久久9999| 激情伊人五月天久久综合| 国产亚洲精品久久久久秋霞| 一本色道久久综合狠狠躁篇| 久久精品国产只有精品66| 老司机国内精品久久久久| 国产69精品久久久久777| 久久久久久九九99精品| 亚洲熟妇无码另类久久久| 狠狠色综合网站久久久久久久高清 | 久久综合视频网站| 欧美久久久久久午夜精品| 精品国产婷婷久久久| 91久久精品无码一区二区毛片| 久久综合久久综合久久综合| 天天久久狠狠色综合| 国产精品嫩草影院久久| 久久久久久久综合日本| 免费久久人人爽人人爽av|