search for: literaln

...es anyway. > > What does "user-defined" means in here? Since the linker can is > involved, I assume it has something to do with the final symbol name. > > At the linker level (symbol names, sections, atoms, relocations, etc), > what exactly that is not supported? The literalN sections were developed long ago to support coalescing of unnamed constants like 9.897 in source code for architectures that could not embed large constants in instructions. The linker could knew how to break up the section (e.g. __literal8 is always 8 byte chunks) and coalesce copies by content....

>> The literalN sections were developed long ago to support coalescing of >> unnamed constants like 9.897 in source code for architectures that could not >> embed large constants in instructions. The linker could knew how to break >> up the section (e.g. __literal8 is always 8 byte chunks) and c...

...ns in here? Since the linker can is >> > involved, I assume it has something to do with the final symbol name. >> > >> > At the linker level (symbol names, sections, atoms, relocations, etc), >> > what exactly that is not supported? >> >> >> The literalN sections were developed long ago to support coalescing of >> unnamed constants like 9.897 in source code for architectures that could >> not embed large constants in instructions. The linker could knew how to >> break up the section (e.g. __literal8 is always 8 byte chunks) and c...

Is there a way to distinguish between GlobalValues that are user-defined and those that are compiler-defined? I am looking for a function that I can use to tell if a GlobalValue is user-defined , something like "GlobalValue::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