Home	Sort by relevance Sort by last modified time

Full Search Definition Symbol File Path History   | | Help

    Searched refs:Floating (Results 1 - 25 of 25) sorted by null

/external/clang/test/SemaCXX/
cxx11-user-defined-literals.cpp	7 Integer, Floating, Raw, Template 18 constexpr LitKind operator"" _kind(long double n) { return LitKind::Floating; } 34 static_assert(.5954_kind == LitKind::Floating, ""); 35 static_assert(1._kind == LitKind::Floating, ""); 36 static_assert(1.e-2_kind == LitKind::Floating, ""); 37 static_assert(4e6_kind == LitKind::Floating, "");
/external/oprofile/events/mips/rm9000/
events	6 event:0x02 counters:0,1 um:zero minimum:500 name:FP_INSTRUCTIONS_ISSUED : Floating-point instructions issued 26 event:0x17 counters:0,1 um:zero minimum:500 name:FP_POSSIBLE_EXCEPTION_CYCLES : Floating-point possible exception cycles
/external/oprofile/events/mips/5K/
events	30 event:0x5 counters:1 um:zero minimum:500 name:FP_INSNS_EXECED : Floating-point instructions executed
/external/llvm/test/MC/PowerPC/
ppc64-encoding-fp.s	5 # Floating-point facility 7 # Floating-point load instructions 40 # Floating-point store instructions 70 # Floating-point move instructions 103 # Floating-point arithmetic instructions 243 # Floating-point rounding and conversion instructions 341 # Floating-point compare instructions 348 # Floating-point select instruction 357 # Floating-point status and control register instructions
/external/llvm/test/MC/AArch64/
arm64-fp-encoding.s	5 ; Floating-point arithmetic 101 ; Floating-point comparison 133 ; Floating-point conditional select 143 ; Floating-point convert 313 ; Floating-point move 365 ; Floating-point round to integral 419 ; Floating-point extract and narrow
arm64-advsimd.s	626 ; AdvSIMD Floating-point <-> Integer Conversions     [all...]
/external/oprofile/events/i386/westmere/
unit_masks	78 0x01 all X87 Floating point assists (Precise Event) 79 0x02 output X87 Floating point assists for invalid output value (Precise Event) 80 0x04 input X87 Floating poiint assists for invalid input value (Precise Event) 82 0x01 x87 Computational floating-point operations executed 91 0x01 to_fp Transitions from MMX to Floating Point instructions 92 0x02 to_mmx Transitions from Floating Point to MMX instructions 93 0x03 any All Floating Point to and from MMX transitions 102 0x02 x87 Retired floating-point operations (Precise Event)
/external/chromium_org/third_party/yasm/source/patched-yasm/modules/objfmts/xdf/tests/
xdflong.asm	143 idesc64 isrL, 0x0008, 0 ; 0x10, 16, #MF, Floating Point Fault 182 dw isrR, 0 ; 0x10, 16, #MF, Floating Point Fault
xdfprotect.asm	117 idesc32 isrP, 0x0008, 0 ; 0x10, 16, #MF, Floating Point Fault 155 dw isrR, 0 ; 0x10, 16, #MF, Floating Point Fault
/external/oprofile/events/i386/atom/
unit_masks	22 0x01 s Floating point computational micro-ops executed 23 0x81 ar Floating point computational micro-ops retired 25 0x81 ar Floating point assists
events	18 event:0x10 counters:0,1 um:x87_comp_ops_exe minimum:6000 name:X87_COMP_OPS_EXE : Floating point computational micro-ops 19 event:0x11 counters:0,1 um:fp_assist minimum:6000 name:FP_ASSIST : Floating point assists
/external/oprofile/events/mips/r10000/
events	16 event:0x05 counters:1 um:zero minimum:500 name:FP_INSTRUCTON_GRADUATED : Floating-point instructions graduated
/external/oprofile/events/mips/rm7000/
events	6 event:0x02 counters:0,1 um:zero minimum:500 name:FP_INSTRUCTIONS_ISSUED : Floating-point instructions issued
/external/chromium_org/testing/gtest/test/
gtest_unittest.cc	[all...]
/external/gtest/test/
gtest_unittest.cc	[all...]
/external/protobuf/gtest/test/
gtest_unittest.cc	[all...]
/ndk/sources/third_party/googletest/googletest/test/
gtest_unittest.cc	[all...]
/external/chromium_org/v8/test/mjsunit/
div-mod.js	52 // Floating point number test.
/external/chromium_org/v8/test/webkit/fast/js/kde/
Array.js	176 // Floating point numbers also should not be treated as valid array indices.
/external/chromium_org/third_party/WebKit/Source/core/rendering/
RenderObject.h	279 // Called when an object that was floating or positioned becomes a normal flow object 535 bool isFloating() const { return m_bitfields.floating(); }     [all...]
/external/openssl/crypto/bn/asm/
pa-risc2.s	37 ; For the floating point registers 926 ; Floating point registers to use to save values that 971 ; Temporary floating point variables, these are all caller save     [all...]
pa-risc2W.s	31 ; For the floating point registers 913 ; Floating point registers to use to save values that 958 ; Temporary floating point variables, these are all caller save     [all...]
/prebuilts/python/darwin-x86/2.7.5/lib/python2.7/pydoc_data/
topics.py	5 'atom-literals': "\nLiterals\n********\n\nPython supports string literals and various numeric literals:\n\n literal ::= stringliteral | integer | longinteger\n | floatnumber | imagnumber\n\nEvaluation of a literal yields an object of the given type (string,\ninteger, long integer, floating point number, complex number) with the\ngiven value. The value may be approximated in the case of floating\npoint and imaginary (complex) literals. See section *Literals* for\ndetails.\n\nAll literals correspond to immutable data types, and hence the\nobject's identity is less important than its value. Multiple\nevaluations of literals with the same value (either the same\noccurrence in the program text or a different occurrence) may obtain\nthe same object or a different object with the same value.\n", 9 'binary': '\nBinary arithmetic operations\n****************************\n\nThe binary arithmetic operations have the conventional priority\nlevels. Note that some of these operations also apply to certain non-\nnumeric types. Apart from the power operator, there are only two\nlevels, one for multiplicative operators and one for additive\noperators:\n\n m_expr ::= u_expr | m_expr "*" u_expr | m_expr "//" u_expr | m_expr "/" u_expr\n | m_expr "%" u_expr\n a_expr ::= m_expr | a_expr "+" m_expr | a_expr "-" m_expr\n\nThe ``*`` (multiplication) operator yields the product of its\narguments. The arguments must either both be numbers, or one argument\nmust be an integer (plain or long) and the other must be a sequence.\nIn the former case, the numbers are converted to a common type and\nthen multiplied together. In the latter case, sequence repetition is\nperformed; a negative repetition factor yields an empty sequence.\n\nThe ``/`` (division) and ``//`` (floor division) operators yield the\nquotient of their arguments. The numeric arguments are first\nconverted to a common type. Plain or long integer division yields an\ninteger of the same type; the result is that of mathematical division\nwith the \'floor\' function applied to the result. Division by zero\nraises the ``ZeroDivisionError`` exception.\n\nThe ``%`` (modulo) operator yields the remainder from the division of\nthe first argument by the second. The numeric arguments are first\nconverted to a common type. A zero right argument raises the\n``ZeroDivisionError`` exception. The arguments may be floating point\nnumbers, e.g., ``3.14%0.7`` equals ``0.34`` (since ``3.14`` equals\n``4*0.7 + 0.34``.) The modulo operator always yields a result with\nthe same sign as its second operand (or zero); the absolute value of\nthe result is strictly smaller than the absolute value of the second\noperand [2].\n\nThe integer division and modulo operators are connected by the\nfollowing identity: ``x == (x/y)*y + (x%y)``. Integer division and\nmodulo are also connected with the built-in function ``divmod()``:\n``divmod(x, y) == (x/y, x%y)``. These identities don\'t hold for\nfloating point numbers; there similar identities hold approximately\nwhere ``x/y`` is replaced by ``floor(x/y)`` or ``floor(x/y) - 1`` [3].\n\nIn addition to performing the modulo operation on numbers, the ``%``\noperator is also overloaded by string and unicode objects to perform\nstring formatting (also known as interpolation). The syntax for string\nformatting is described in the Python Library Reference, section\n*String Formatting Operations*.\n\nDeprecated since version 2.3: The floor division operator, the modulo\noperator, and the ``divmod()`` function are no longer defined for\ncomplex numbers. Instead, convert to a floating point number using\nthe ``abs()`` function if appropriate.\n\nThe ``+`` (addition) operator yields the sum of its arguments. The\narguments must either both be numbers or both sequences of the same\ntype. In the former case, the numbers are converted to a common type\nand then added together. In the latter case, the sequences are\nconcatenated.\n\nThe ``-`` (subtraction) operator yields the difference of its\narguments. The numeric arguments are first converted to a common\ntype.\n',     [all...]
/prebuilts/python/linux-x86/2.7.5/lib/python2.7/pydoc_data/
topics.py	5 'atom-literals': "\nLiterals\n********\n\nPython supports string literals and various numeric literals:\n\n literal ::= stringliteral | integer | longinteger\n | floatnumber | imagnumber\n\nEvaluation of a literal yields an object of the given type (string,\ninteger, long integer, floating point number, complex number) with the\ngiven value. The value may be approximated in the case of floating\npoint and imaginary (complex) literals. See section *Literals* for\ndetails.\n\nAll literals correspond to immutable data types, and hence the\nobject's identity is less important than its value. Multiple\nevaluations of literals with the same value (either the same\noccurrence in the program text or a different occurrence) may obtain\nthe same object or a different object with the same value.\n", 9 'binary': '\nBinary arithmetic operations\n****************************\n\nThe binary arithmetic operations have the conventional priority\nlevels. Note that some of these operations also apply to certain non-\nnumeric types. Apart from the power operator, there are only two\nlevels, one for multiplicative operators and one for additive\noperators:\n\n m_expr ::= u_expr | m_expr "*" u_expr | m_expr "//" u_expr | m_expr "/" u_expr\n | m_expr "%" u_expr\n a_expr ::= m_expr | a_expr "+" m_expr | a_expr "-" m_expr\n\nThe ``*`` (multiplication) operator yields the product of its\narguments. The arguments must either both be numbers, or one argument\nmust be an integer (plain or long) and the other must be a sequence.\nIn the former case, the numbers are converted to a common type and\nthen multiplied together. In the latter case, sequence repetition is\nperformed; a negative repetition factor yields an empty sequence.\n\nThe ``/`` (division) and ``//`` (floor division) operators yield the\nquotient of their arguments. The numeric arguments are first\nconverted to a common type. Plain or long integer division yields an\ninteger of the same type; the result is that of mathematical division\nwith the \'floor\' function applied to the result. Division by zero\nraises the ``ZeroDivisionError`` exception.\n\nThe ``%`` (modulo) operator yields the remainder from the division of\nthe first argument by the second. The numeric arguments are first\nconverted to a common type. A zero right argument raises the\n``ZeroDivisionError`` exception. The arguments may be floating point\nnumbers, e.g., ``3.14%0.7`` equals ``0.34`` (since ``3.14`` equals\n``4*0.7 + 0.34``.) The modulo operator always yields a result with\nthe same sign as its second operand (or zero); the absolute value of\nthe result is strictly smaller than the absolute value of the second\noperand [2].\n\nThe integer division and modulo operators are connected by the\nfollowing identity: ``x == (x/y)*y + (x%y)``. Integer division and\nmodulo are also connected with the built-in function ``divmod()``:\n``divmod(x, y) == (x/y, x%y)``. These identities don\'t hold for\nfloating point numbers; there similar identities hold approximately\nwhere ``x/y`` is replaced by ``floor(x/y)`` or ``floor(x/y) - 1`` [3].\n\nIn addition to performing the modulo operation on numbers, the ``%``\noperator is also overloaded by string and unicode objects to perform\nstring formatting (also known as interpolation). The syntax for string\nformatting is described in the Python Library Reference, section\n*String Formatting Operations*.\n\nDeprecated since version 2.3: The floor division operator, the modulo\noperator, and the ``divmod()`` function are no longer defined for\ncomplex numbers. Instead, convert to a floating point number using\nthe ``abs()`` function if appropriate.\n\nThe ``+`` (addition) operator yields the sum of its arguments. The\narguments must either both be numbers or both sequences of the same\ntype. In the former case, the numbers are converted to a common type\nand then added together. In the latter case, the sequences are\nconcatenated.\n\nThe ``-`` (subtraction) operator yields the difference of its\narguments. The numeric arguments are first converted to a common\ntype.\n',     [all...]
/external/bison/
configure	[all...]

Completed in 1825 milliseconds