Displaying 7 results from an estimated 7 matches for "exported_symbols".
2010 Oct 13
1
[LLVMdev] Compile or link error
....dll by perfoming 'make' in
$LLVM_SRC_DIR/runtime/libprofile. After make, I got the following error
messages.
llvm[0]: Linking Debug+Asserts Loadable Module profile_rt.dll
/usr/lib/gcc/i686-pc-cygwin/4.3.4/../../../../i686-pc-cygwin/bin/ld:/cygdrive/c/
llvm/runtime/libprofile/Debug+Asserts/exported_symbols.lst: file format not
reco
gnized; treating as linker script
/usr/lib/gcc/i686-pc-cygwin/4.3.4/../../../../i686-pc-cygwin/bin/ld:/cygdrive/c/
llvm/runtime/libprofile/Debug+Asserts/exported_symbols.lst:2: syntax error
collect2: ld returned 1 exit status
make: *** [/cygdrive/c/llvm/Debug+Asserts/bin/p...
2009 Jan 26
0
[LLVMdev] -O4 -fvisibility=hidden
...owing
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 approach, pl. read ld man page first.
-
Devang
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 Sep 01
1
[LLVMdev] Problem building libprofile.
...libc.so.6 0x00002aaaabaaf1a6 __libc_start_main + 230
22 llvm-ld 0x00000000006aa039 __gxx_personality_v0 + 689
Stack dump:
0. Program arguments: .../llvm-svn-debug-obj/Debug/bin/llvm-ld
-L.../llvm-van-install/bin/../lib
-internalize-public-api-file=.../llvm-svn/runtime/libprofile/exported_symbols.lst
-o
.../llvm-svn-debug-obj/runtime/libprofile/Debug/profile_rt.internalize
.../llvm-svn-debug-obj/runtime/libprofile/Debug/BasicBlockTracing.bc
.../llvm-svn-debug-obj/runtime/libprofile/Debug/BlockProfiling.bc
.../llvm-svn-debug-obj/runtime/libprofile/Debug/CommonProfiling.bc
.../llvm-svn-debug-...
2009 Jan 31
2
[LLVMdev] -O4 -fvisibility=hidden
...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 approach, pl. read ld man page first.
> -
> Devang
>
>
>
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu...
2018 Dec 07
2
using emulated-tls on Darwin 8, 9, 10
Please excuse hobbiest-level question.
Darwin 11+ enables thread_local variables using system-level supports.
I have an interest in enabling TLS on darwin < 11 using emulated-tls. This can be enabled with a few modest patches:
==========================
--- a/include/llvm/ADT/Triple.h.orig 2018-10-02 17:38:10.000000000 -0700
+++ b/include/llvm/ADT/Triple.h 2018-10-02 17:38:58.000000000
2017 Jun 07
3
LLD support for ld64 mach-o linker synthesised symbols
On Tue, Jun 6, 2017 at 11:14 PM, Michael Clark via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> OK. I see that the Mach-O linker is not even built when LLD is enabled in
> Release_40, only the PE/COFF and ELF linkers are built.
>
> From looking at reviews it appears that Clang was able to be linked with
> LLD on Darwin about 2 years ago, so Mach-O support seems to have