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

            導航

            <2012年8月>
            2930311234
            567891011
            12131415161718
            19202122232425
            2627282930311
            2345678

            統計

            常用鏈接

            留言簿

            隨筆分類

            隨筆檔案

            文章分類

            文章檔案

            my

            搜索

            最新評論

            閱讀排行榜

            評論排行榜

            久久99精品久久久久久久不卡| 麻豆亚洲AV永久无码精品久久| 夜夜亚洲天天久久| 亚洲午夜久久影院| 亚洲天堂久久久| 久久精品午夜一区二区福利| 久久午夜电影网| 无码任你躁久久久久久久| 久久久久亚洲av成人网人人软件 | 亚洲精品高清久久| 欧美国产精品久久高清| 97精品依人久久久大香线蕉97| 久久精品国产一区| 久久亚洲国产精品五月天婷| 亚洲国产精品18久久久久久| 国产精品亚洲综合专区片高清久久久| 欧美日韩精品久久久免费观看| 久久香蕉国产线看观看乱码| 国产精品久久久久久久久软件| 久久精品草草草| 国产aⅴ激情无码久久| 久久香蕉一级毛片| 精品乱码久久久久久久| 无码国内精品久久人妻麻豆按摩 | 国产∨亚洲V天堂无码久久久| 久久久免费观成人影院| 99麻豆久久久国产精品免费 | 国内精品久久久久久中文字幕| 亚洲人成网亚洲欧洲无码久久| 久久久精品视频免费观看| 91精品国产综合久久婷婷| 日韩人妻无码精品久久免费一 | 成人国内精品久久久久一区| 武侠古典久久婷婷狼人伊人| 狠狠色丁香婷婷综合久久来来去| 久久婷婷五月综合国产尤物app | 狠狠88综合久久久久综合网 | 人妻精品久久久久中文字幕69| 一本色综合久久| 亚洲精品高清国产一线久久| 久久久久久免费视频|