search for: __literaln

Displaying 4 results from an estimated 4 matches for "__literaln".

Did you mean: __literal8
2014 Aug 25
4
[LLVMdev] How to tell whether a GlobalValue is user-defined
...hem to the same address. For whatever reason, we could not fix gcc, so we changed to linker to never coalesce items in literal sections if there was a (non ‘L’ and non ‘l’) symbol on it. The current state of LLVM is that is it going out of its way to move “named” constants from __const section to __literalN section. But the only possible advantage to doing that is that the hopes that the linker might coalesce it. But the linker won’t coalesce it because it is named. So, is there a way to keep the named values in the __const section? -Nick
2014 Aug 27
2
[LLVMdev] How to tell whether a GlobalValue is user-defined
..., so we changed to linker to never coalesce items in literal sections if >> there was a (non ‘L’ and non ‘l’) symbol on it. > > > Thanks for the info! +1 >> The current state of LLVM is that is it going out of its way to move >> “named” constants from __const section to __literalN section. But the only >> possible advantage to doing that is that the hopes that the linker might >> coalesce it. But the linker won’t coalesce it because it is named. So, is >> there a way to keep the named values in the __const section? > > > Right, LLVM has proven th...
2014 Aug 25
2
[LLVMdev] How to tell whether a GlobalValue is user-defined
...n, we could >> not fix gcc, so we changed to linker to never coalesce items in literal >> sections if there was a (non ‘L’ and non ‘l’) symbol on it. >> >> The current state of LLVM is that is it going out of its way to move >> “named” constants from __const section to __literalN section. But the only >> possible advantage to doing that is that the hopes that the linker might >> coalesce it. But the linker won’t coalesce it because it is named. So, is >> there a way to keep the named values in the __const section? >> > > I believe the followi...
2014 Aug 21
3
[LLVMdev] How to tell whether a GlobalValue is user-defined
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