search for: cppruntimeenv

Displaying 3 results from an estimated 3 matches for "cppruntimeenv".

2009 Jan 26
0
[LLVMdev] -O4 -fvisibility=hidden
...e way to control symbol visibility is to use gcc's (inherited by llvm-gcc) visibility support. GCC supports, 1) command line options 2) attributes and 3) pragmas in this regard. Following document provides good summary... http://developer.apple.com/documentation/DeveloperTools/Conceptual/CppRuntimeEnv/Articles/SymbolVisibility.html#/ /apple_ref/doc/uid/TP40001670 Another way to control symbol visibility is to use linker's interface. See ld man page for more info on -exported_symbols_list, - exported_symbols, -unexported_symbols_list etc.. flags. If you're going to try this approac...
2009 Jan 25
2
[LLVMdev] -O4 -fvisibility=hidden
On Sun, Jan 25, 2009 at 11:38:48AM +0100, Jean-Daniel Dupas wrote: > > Le 25 janv. 09 à 06:01, Jack Howarth a écrit : > > > After trying the recommended use of -O4 -fvisibility=hidden to > > compile xplor-nih with full LTO optimizations, I discovered three > > symbols become undefined... > > > > llvm-gcc-4 -O4 -fvisibility=hidden -o xplor xplor.o \ >
2009 Jan 31
2
[LLVMdev] -O4 -fvisibility=hidden
...isibility is to use gcc's > (inherited by llvm-gcc) visibility support. GCC supports, 1) command > line options 2) attributes and 3) pragmas in this regard. Following > document provides good summary... > > http://developer.apple.com/documentation/DeveloperTools/Conceptual/CppRuntimeEnv/Articles/SymbolVisibility.html#/ > /apple_ref/doc/uid/TP40001670 > > Another way to control symbol visibility is to use linker's interface. > See ld man page for more info on -exported_symbols_list, - > exported_symbols, -unexported_symbols_list etc.. flags. If you're...