Displaying 2 results from an estimated 2 matches for "hidden_symbol_2".
Did you mean:
hidden_symbol_1
2016 Jun 13
5
[RFC] Embedded bitcode and related upstream (Part II)
...ure the bitcode after symbol hiding pass can still link and produce the same output, the pass need to rename them:
a.o:
T export_symbol --> export_symbol (preserve)
T global_symbol --> hidden_symbol_1 (rename, but need to have the same name as the one in b.o)
t local_symbol --> hidden_symbol_2 (rename, but don't care what it becomes)
b.o:
U global_symbol --> hidden_symbol_1
The pass need to know what symbols to keep and a global renaming table so the names after renaming are consistent across all the modules.
>
> 4. Debug info strip to line-tables pass:
> As the nam...
2016 Jun 03
6
[RFC] Embedded bitcode and related upstream (Part II)
Hi everyone
I am still in the process of upstreaming some improvements to the embed bitcode option. If you want more background, you can read the previous RFC (http://lists.llvm.org/pipermail/llvm-dev/2016-February/094851.html <http://lists.llvm.org/pipermail/llvm-dev/2016-February/094851.html>). This is part II of the discussion.
Current Status:
A basic version of -fembed-bitcode option