Searched refs:lvalues (Results 1 – 8 of 8) sorted by relevance
/dflybsd-src/crypto/libressl/crypto/objects/ |
H A D | obj_dat.h | 70 static const unsigned char lvalues[6699]={ variable 1016 {"rsadsi","RSA Data Security, Inc.",NID_rsadsi,6,&(lvalues[0]),0}, 1017 {"pkcs","RSA Data Security, Inc. PKCS",NID_pkcs,7,&(lvalues[6]),0}, 1018 {"MD2","md2",NID_md2,8,&(lvalues[13]),0}, 1019 {"MD5","md5",NID_md5,8,&(lvalues[21]),0}, 1020 {"RC4","rc4",NID_rc4,8,&(lvalues[29]),0}, 1021 {"rsaEncryption","rsaEncryption",NID_rsaEncryption,9,&(lvalues[37]),0}, 1023 &(lvalues[46]),0}, 1025 &(lvalues[55]),0}, 1027 &(lvalues[64]),0}, [all …]
|
/dflybsd-src/contrib/gcc-4.7/libstdc++-v3/include/std/ |
H A D | future | 390 // set lvalues
|
H A D | functional | 1595 // std::bind always forwards bound arguments as lvalues,
|
/dflybsd-src/contrib/gcc-8.0/libstdc++-v3/include/std/ |
H A D | future | 461 // set lvalues
|
/dflybsd-src/contrib/gcc-4.7/gcc/doc/ |
H A D | rtl.texi | 180 and are lvalues (so they can be used for insertion as well). 380 All the macros defined in this section expand into lvalues and therefore 566 are accessed with the following macros, which expand into lvalues. 1790 Paradoxical @code{subreg}s can be used as both lvalues and rvalues. 2586 Unlike @code{sign_extract}, this type of expressions can be lvalues
|
H A D | gimple.texi | 477 Currently compound lvalues involving array and structure field references
|
H A D | generic.texi | 114 values are lvalues.
|
H A D | extend.texi | 1694 In ISO C99, arrays that are not lvalues still decay to pointers, and 5815 Output operand expressions must be lvalues; the compiler can check this. 5816 The input operands need not be lvalues. The compiler cannot check 14945 are lvalues, and if used as an lvalue, the volatile object will be
|