search for: __literal16

...alValue::isUserDefined", which returns true for user-defined GlobalValue. I'm trying to make changes to prevent llvm from placing user-defined constant arrays in the merge able constant sections. Currently, clang places 16-byte constant arrays that are marked "unnamed_addr" into __literal16 for macho (see following example). $ cat test1.c static const int s_dashArraysSize1[4] = {2, 2, 4, 6}; int foo1(int a) { return s_dashArraysSize1[a]; } $ clang test1.c -S -O3 -o - | tail -n 10 .section __TEXT,__literal16,16byte_literals .align 4 ## @s_dashArraysSize...

...rue for user-defined >> GlobalValue. >> >> I'm trying to make changes to prevent llvm from placing user-defined >> constant arrays in the merge able constant sections. Currently, clang places >> 16-byte constant arrays that are marked "unnamed_addr" into __literal16 for >> macho (see following example). >> >> $ cat test1.c >> >> static const int s_dashArraysSize1[4] = {2, 2, 4, 6}; >> >> >> int foo1(int a) { >> >> return s_dashArraysSize1[a]; >> >> } >> >> >> $ c...

...gt;> >> >> I'm trying to make changes to prevent llvm from placing user-defined >> >> constant arrays in the merge able constant sections. Currently, clang >> places >> >> 16-byte constant arrays that are marked "unnamed_addr" into >> __literal16 for >> >> macho (see following example). >> >> >> >> $ cat test1.c >> >> >> >> static const int s_dashArraysSize1[4] = {2, 2, 4, 6}; >> >> >> >> >> >> int foo1(int a) { >> >> >> >&gt...

...seDirectiveSectionSwitch("__TEXT", "__literal8", - MCSectionMachO::S_8BYTE_LITERALS, - 8); - if (IDVal == ".literal16") - return ParseDirectiveSectionSwitch("__TEXT","__literal16", - MCSectionMachO::S_16BYTE_LITERALS, - 16); - if (IDVal == ".constructor") - return ParseDirectiveSectionSwitch("__TEXT","__constructor"); - if (IDVal == ".destructor...