What makes signed integers behave differently?

Posted by 000 on Programmers See other posts from Programmers or by 000
Published on 2012-09-14T16:59:27Z Indexed on 2012/09/14 21:47 UTC
Read the original article Hit count: 313

Filed under:

assembly

In this example of x86_64 hex/disassembled code I see:

48B80000000000000000 mov rax, 0x0

    Signed Byte 52
    Unsigned Byte   52
    Signed Short    14388
    Unsigned Short  14388
    Signed Int  943863860
    Unsigned Int    943863860
    Signed Int64    3472328296363079732
    Unsigned Int64  3472328296363079732
    Float   4.630555e-05
    Double  1.39804332763832e-76
    String  48B80000000000000000

which to me appears to have the same functionality as:

48C7C000000000 mov rax, 0x0

    48C7C000000000

    Signed Byte 52
    Unsigned Byte   52
    Signed Short    14388
    Unsigned Short  14388
    Signed Int  927152180
    Unsigned Int    927152180
    Signed Int64    3472328377950746676
    Unsigned Int64  3472328377950746676
    Float   1.163599e-05
    Double  1.39806836023098e-76
    String  48C7C000000000

How is the first example treated differently from the second example?

Related posts about assembly

More information wanted on error: CREATE ASSEMBLY for assembly failed because assembly failed verif

as seen on Stack Overflow - Search for 'Stack Overflow'
I have a small application that uses SQL Server 2005 Express with CLR stored procedures. It has been successfully installed and runs on many computers running XP and Vista. To create the assembly the following SQL is executed (names changed to protect the innocent): CREATE ASSEMBLY myAssemblyName… >>> More
Installed SQL Server 2008 and now TFS is broken.

as seen on Server Fault - Search for 'Server Fault'
Hi, My W2K3 server was running TFS 2008 SP1, SQL Server 2005 Development edition. I installed SQL Server 2008 Standard. I installed it while leaving SQL Server 2005 alone. Upgrading was not possible due to the differences in editions of the SQL Servers. Now TFS is broken. On a client computer… >>> More
How to Specify AssemblyKeyFile Attribute in .NET Assembly and Issues

as seen on Microsoft .NET Support Team - Search for 'Microsoft .NET Support Team'
How to specify strong key file in assembly? Answer: You can specify snk file information using following line [assembly: AssemblyKeyFile(@"c:\Key2.snk")] Where to specify an strong key file (snk file)? Answer: You have two options to specify the AssemblyKeyFile infromation. 1. In… >>> More
Assembly Language Question: Display Characters to screen LIFO (Last In First Out) in assembly langua

as seen on Stack Overflow - Search for 'Stack Overflow'
Given a stack that displays characters to the screen First in First Out(FIFO), how do you switch it to display them Last in First Out(LIFO). Theoretically speaking... is it simply just sending the characters to print in reverse order? >>> More
c# - can you make a "weak" assembly reference to a strong named assembly

as seen on Stack Overflow - Search for 'Stack Overflow'
hi, for various reasons i would rather not use strong named (signed) assemblies in my project. however, one of the projects is referenced by a sharepoint web part which means it must be signed. is it possible to have this assembly signed but when I reference it from other projects, to do so using… >>> More

Developer IT

What makes signed integers behave differently? - Developer IT

What makes signed integers behave differently?

assembly

Related posts about assembly

More information wanted on error: CREATE ASSEMBLY for assembly failed because assembly failed verif

Installed SQL Server 2008 and now TFS is broken.

How to Specify AssemblyKeyFile Attribute in .NET Assembly and Issues

Assembly Language Question: Display Characters to screen LIFO (Last In First Out) in assembly langua

c# - can you make a "weak" assembly reference to a strong named assembly

Categories cloud