

Technical Support OnLine Manuals C251 User's Guide C251 Introduction Compiling Programs Language Extensions Preprocessor Advanced Programming Customization Files Startup Code Variable Initialization Code Basic I/O Memory Allocation Optimizer General Optimizations 251Specific Optimizations Options for Code Generation Global Register Coloring Segment Naming Conventions Segment Types Initialization Segments Function Symbols Parameter Passing Symbols Hardware Stack Calculating Stack Size Interfacing C Programs to Assembler Global Variables Function Parameters Passing in Memory Passing in Registers Function Return Values Using the SRC Directive Register Usage Overlaying Segments TINY Model XTINY Model SMALL Model XSMALL Model LARGE Model Data Storage Formats Bit Variables 1Byte Scalars 2Byte Scalars 4Byte Scalars Floatingpoint Numbers Floatingpoint Errors Double Numbers Double Errors Absolute Memory Locations Absolute Access Macros Linker Location Controls The _at_ Keyword Debugging Error Messages Library Reference Appendix 
Floatingpoint NumbersScalars of type float are stored using four bytes (32bits). float type numbers have a precision of 24 bits, which represents about 7 decimal digits. The format used follows the IEEE754 standard. A floatingpoint number is expressed as the product of two parts: the mantissa and the exponent. For example: ±mantissa × 2^{exponent} The mantissa represents the actual binary digits of the floatingpoint number. The exponent is represented by the power of two. The exponent is an 8bit value from 0 to 255 and is stored relative to 127. The actual value of the exponent is calculated by subtracting 127 from the stored value (0 to 255), giving a range of –127 to +128. The mantissa is a 24bit value (representing about seven decimal digits) whose most significant bit (MSB) is always 1 and is, therefore, not stored. There is also a sign bit that indicates whether the floatingpoint number is positive or negative. Floatingpoint numbers are stored on byte boundaries in the following format:
Where
Zero is a special value denoted with an exponent field of 0 and a mantissa of 0. Using the above format, the floatingpoint number 12.5 is stored as a hexadecimal value of 0xC1480000. In memory, this value appears as follows:
It is fairly simple to convert floatingpoint numbers to and from their hexadecimal storage equivalents. The following example demonstrates how this is done for the value 12.5 shown above. The floatingpoint storage representation is not an intuitive format. To convert this to a floatingpoint number, the bits must be separated as specified in the floatingpoint number storage format table shown above. For example:
From this illustration, you can determine the following:
There is an understood binary/decimal point at the left of the mantissa that is always preceded by a 1. This digit is omitted from the stored form of the floatingpoint number. Adding 1 and the binary/decimal point to the beginning of the mantissa gives the following value: 1.10010000000000000000000 To adjust the mantissa for the exponent, move the decimal point to the left for negative exponent values or right for positive exponent values. Since the exponent is three, the mantissa is adjusted as follows: 1100.10000000000000000000 The result is a binary floatingpoint number. Binary digits to the left of the decimal point represent the power of two corresponding to their position. For example, 1100 represents (1 × 2^{3}) + (1 × 2^{2}) + (0 × 2^{1}) + (0 × 2^{0}), which is 12. Binary digits to the right of the decimal point also represent the power of two corresponding to their position. However, because these digits are tto the right of the decimal point, the powers are negative. For example, .100... represents (1 × 2^{1}) + (0 × 2^{2}) + (0 × 2^{3}) + ... which equals .5. The sum of these values is 12.5. Because the sign bit was set, this number should be negative. So, the hexadecimal value 0xC1480000 is 12.5.  

Arm’s Privacy Policy has been updated. By continuing to use our site, you consent to Arm’s Privacy Policy. Please review our Privacy Policy to learn more about our collection, use and transfers
of your data.