Searched refs:v1 (Results 1 – 9 of 9) sorted by relevance
43 extern "C" const char* v1 = "unset";52 return choice == nullptr ? &v1 : &v2; in foo_ifunc()
953 // lib v1 - this one used during static linking but never used at runtime954 // which forces libtest_versioned_uselibv1 to use function v1 from
40 } v1; member
61 v1 = 1.10958421e+00, /* 0x3f8e06db */ variable183 p2 = one+y*(v1+y*(v2+y*v3)); in __ieee754_lgammaf_r()
132 v1 = 2.45597793713041134822e+00, /* 0x4003A5D7, 0xC2BD619C */ variable267 p2 = one+y*(v1+y*(v2+y*(v3+y*(v4+y*v5)))); in __ieee754_lgamma_r()
470 Android Native Heap Dump v1.0522 Android P produces version v1.1 of the heap dump.524 Android Native Heap Dump v1.1526 The only difference between v1.0 and v1.1 is that the NUM\_ALLOCATIONS527 value is always accurate in v1.1. A previous version of malloc debug set528 NUM\_ALLOCATIONS to an incorrect value. For heap dump v1.0, the532 Android Q introduces v1.2 of the heap dump. The new header looks like this:534 Android Native Heap Dump v1.2541 The new version no longer 0 pads the backtrace addresses. In v1.0/v1.1:545 While v1.2:
70 struct fscrypt_policy_v1 v1; member
121 v1 = 5.15937098592887275994320496999951947e+00L, variable293 p2 = one+y*(v1+y*(v2+y*(v3+y*(v4+y*(v5+y*(v6+y*(v7+ in lgammal_r()
145 } __attribute__((packed)) v1; member