search for: _s_dasharrayssize1

...>> >> >> >> >> >> $ clang test1.c -S -O3 -o - | tail -n 10 >> >> >> >> .section __TEXT,__literal16,16byte_literals >> >> >> >> .align 4 ## @s_dashArraysSize1 >> >> >> >> _s_dashArraysSize1: >> >> >> >> .long 2 ## 0x2 >> >> >> >> .long 2 ## 0x2 >> >> >> >> .long 4 ## 0x4 >> >> >> >> .long 6 ## 0x6 >&g...

...r 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_dashArraysSize1 _s_dashArraysSize1: .long 2 ## 0x2 .long 2 ## 0x2 .long 4 ## 0x4 .long 6 ## 0x6 This is not desirable because macho linker wasn't originally designed to handle user-defined symbols in those sections and having to handle...

...a) { >> >> return s_dashArraysSize1[a]; >> >> } >> >> >> $ clang test1.c -S -O3 -o - | tail -n 10 >> >> .section __TEXT,__literal16,16byte_literals >> >> .align 4 ## @s_dashArraysSize1 >> >> _s_dashArraysSize1: >> >> .long 2 ## 0x2 >> >> .long 2 ## 0x2 >> >> .long 4 ## 0x4 >> >> .long 6 ## 0x6 >> >> >> >> This is not desirable because macho...