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

            導航

            <2025年5月>
            27282930123
            45678910
            11121314151617
            18192021222324
            25262728293031
            1234567

            統計

            常用鏈接

            留言簿

            隨筆分類

            隨筆檔案

            文章分類

            文章檔案

            my

            搜索

            最新評論

            閱讀排行榜

            評論排行榜

            日批日出水久久亚洲精品tv| 91超碰碰碰碰久久久久久综合| 7777精品久久久大香线蕉| 久久综合给合综合久久| 97久久国产综合精品女不卡 | 亚洲av成人无码久久精品| 国产亚洲欧美成人久久片| 亚洲国产精品成人AV无码久久综合影院 | 72种姿势欧美久久久久大黄蕉| 久久99九九国产免费看小说| 久久无码人妻一区二区三区| 久久精品无码专区免费 | 久久国产精品久久| 97精品伊人久久大香线蕉| 久久久九九有精品国产| 国内精品久久久人妻中文字幕| 一本久久综合亚洲鲁鲁五月天亚洲欧美一区二区 | 久久综合九色综合精品| 久久精品一区二区三区AV| 午夜精品久久久久成人| 国产91色综合久久免费分享| 精品伊人久久久| 久久WWW免费人成—看片| 大美女久久久久久j久久| 99久久人妻无码精品系列蜜桃| 久久影视综合亚洲| 久久国产精品国语对白| 国产精品久久久久久久久| 7777久久久国产精品消防器材| 欧美久久一级内射wwwwww.| 一级做a爰片久久毛片人呢| 99久久免费国产精品热| 蜜臀久久99精品久久久久久小说| 一级做a爰片久久毛片看看| 精品久久久久久国产牛牛app| 97久久久久人妻精品专区| 日韩AV无码久久一区二区| 亚洲AV无一区二区三区久久| 久久久久久久久久久| 久久久精品人妻一区二区三区蜜桃 | 午夜久久久久久禁播电影|