search for: dsos

Displaying 20 results from an estimated 128 matches for "dsos".

Did you mean: dso
1999 Aug 03
2
compliation problem
Problem compiling R. version: 0.64.2 machine: SGI O2 OS: IRIX6.5 CC cc FC f77 MAKE GNU make 3.75 Here is part of the the output for make. make[2]: Leaving directory `/usr/people/faculty/math/mgass/stage/R/R-0.64.2/src/include' make[2]: Entering directory `/usr/people/faculty/math/mgass/stage/R/R-0.64.2/src/appl' cc -g -OPT:IEEE_NaN_inf=ON -I../include
2018 Sep 26
2
[RFC] Proposal: llvm-tapi, adding YAML/stub generation for ELF linking support
Right. Usually you wouldn't want to write a .tbe from scratch, but for the sake of linking against a DSO you might only have access to a .tbe stub that was produced from the DSO. This specific functionality becomes critical when DSOs only used for linking are replaced entirely by .tbe stubs because at a SDK level the complete DSO isn't needed. This is what Apple has done to significantly reduce their SDK size. The .tbe format brings linking functionality, readability, and smaller size than a stripped ELF file, making them s...
2012 Dec 07
2
[LLVMdev] [MC] [llvm-mc] Getting target specific information to <target>ELFObjectWriter
Hi Rafael, There are a lot of flags. Here are the ones you ask about: -KPIC, -call_shared generate SVR4 position independent code -call_nonpic generate non-PIC code that can operate with DSOs -mvxworks-pic generate VxWorks position independent code -non_shared do not generate code that can operate with DSOs -xgot assume a 32 bit GOT Just to make things fun, the SGI notion of cpic (call pic) fits gnu's -call_nonpic. Remember, this issue is not whether the direct or standalone as...
2018 Sep 26
2
[RFC] Proposal: llvm-tapi, adding YAML/stub generation for ELF linking support
...the tool is to produce both textual and binary DSO stubs. This means you could take a DSO, produce a textual stub, modify it however you wish, and then produce a linkable binary stub from that modified .tbe. That, or you could bypass the textual portion altogether and just produce binary stubs from DSOs. While the textual format is useful, the goal is to make the tool complete and maximally applicable by producing ELF stubs as well. Alphabetical symbol sorting is currently a part of the plan as well. It makes producing a diff easier as well. On Wed, Sep 26, 2018 at 9:51 AM Rui Ueyama <ruiu at...
2012 Dec 08
0
[LLVMdev] [MC] [llvm-mc] Getting target specific information to <target>ELFObjectWriter
...ecember 2012 18:57, Carter, Jack <jcarter at mips.com> wrote: > Hi Rafael, > > There are a lot of flags. Here are the ones you ask about: > > -KPIC, -call_shared generate SVR4 position independent code > -call_nonpic generate non-PIC code that can operate with DSOs > -mvxworks-pic generate VxWorks position independent code > -non_shared do not generate code that can operate with DSOs > -xgot assume a 32 bit GOT > > Just to make things fun, the SGI notion of cpic (call pic) fits gnu's -call_nonpic. Awesome. A...
2017 Dec 02
2
[LLD] Slow callstacks in gdb
...t a reproducible. I tried gdb on clang itself >> build with both clang and gcc and linked with gold and lld. I could not >> reproduce the slowdown, but I was using trunk lld. > > I will retry with clang trunk, when it reproduces I will build some other > large project (that has DSOs) using our compile/link options (they are not > that special, I think). If you can try lld trunk too that would be awesome. Cheers, Rafael
2019 Jun 13
4
Need help on identifying a patch which fixed lld on linux platform
Hi All, This test is on a ubuntu 12 box. Can anyone please point me what revision/commit-id of lld fixed this issue which was atleast in llvm 5.0. . ├── build.sh ├── main.c ├── shared │ └── sh.c └── static └── st.c [[ build.sh ]] #!/bin/sh CC="${TOOLCHAIN}/bin/clang" AR="${TOOLCHAIN}/bin/llvm-ar" CFLAGS="-g -O" LDFLAGS="-fuse-ld=lld" rm
2016 Mar 11
3
RFC: A new ABI for virtual calls, and a change to the virtual call representation in the IR
...s, but that would introduce an additional level of indirection and additional relocations, probably costing us more in binary size and memory bandwidth than the current ABI. >> >> However, it is technically possible to split the implementation of a class's virtual functions between DSOs, and there are more practical cases where we might expect to see cross-DSO references: >> >> - one DSO could derive from a class defined in another DSO, and only override some of its virtual functions >> - the vtable could contain a reference to __cxa_pure_virtual which would be...
2012 Dec 10
2
[LLVMdev] [MC] [llvm-mc] Getting target specific information to <target>ELFObjectWriter
...ecember 2012 18:57, Carter, Jack <jcarter at mips.com> wrote: > Hi Rafael, > > There are a lot of flags. Here are the ones you ask about: > > -KPIC, -call_shared generate SVR4 position independent code > -call_nonpic generate non-PIC code that can operate with DSOs > -mvxworks-pic generate VxWorks position independent code > -non_shared do not generate code that can operate with DSOs > -xgot assume a 32 bit GOT > > Just to make things fun, the SGI notion of cpic (call pic) fits gnu's -call_nonpic. Awesome. A...
2019 Feb 27
14
RFC: Linker feature for automatically partitioning a program into multiple binaries
...st point. == Proposed solution == I propose to extend lld so that it can perform the required partitioning automatically, given a set of entry points for each part of the program. The end product of linking will be a main program (which can be either an executable or a DSO) combined with a set of DSOs that must be loaded at fixed addresses relative to the base address of the main program. These binaries will all share a virtual address space so that they can refer to one another directly using PC-relative references or RELATIVE dynamic relocations as if they were all statically linked together i...
2018 Sep 26
4
[RFC] Proposal: llvm-tapi, adding YAML/stub generation for ELF linking support
...tools. This does not strive to replace tools altogether; it just makes small tasks significantly more approachable. llvm-tapi would strive to be an intersection between a means to produce and link against stubs, and providing tools that offer more control and insight into the public interfaces of DSOs. More fundamentally, llvm-tapi would introduce a library to generate and ingest human-readable stubs from DSOs to address these issues directly in LLVM. Overall, this idea is most similar to the vein of Apple’s TAPI, as the original TAPI also uses human-readable stubs. In general, llvm-tapi should...
2019 Mar 02
2
RFC: Linker feature for automatically partitioning a program into multiple binaries
...>> I propose to extend lld so that it can perform the required partitioning >> automatically, given a set of entry points for each part of the program. >> The end product of linking will be a main program (which can be either an >> executable or a DSO) combined with a set of DSOs that must be loaded at >> fixed addresses relative to the base address of the main program. These >> binaries will all share a virtual address space so that they can refer to >> one another directly using PC-relative references or RELATIVE dynamic >> relocations as if they w...
2018 Feb 07
2
ThinLTO and linkonce_odr + unnamed_addr
...pting MachO into -fvisibility-inlines-hidden all the time, i.e. if the function is linkonce, it's discardable, so mark it hidden to pretend the compiler inlined it and discarded it. However, this isn't conforming, because the addresses of inline functions will no longer compare equal across DSOs. I think there is a nuance, it is marking these as "auto-hide": it just means that the address is not taken in the current compilation unit IIRC. The linker decides that it can hide it in the DSO if none of the compilation unit is using the address based on this auto-hide flag. Does it...
2012 Dec 11
0
[LLVMdev] [MC] [llvm-mc] Getting target specific information to <target>ELFObjectWriter
..., Jack <jcarter at mips.com> wrote: >> Hi Rafael, >> >> There are a lot of flags. Here are the ones you ask about: >> >> -KPIC, -call_shared generate SVR4 position independent code >> -call_nonpic generate non-PIC code that can operate with DSOs >> -mvxworks-pic generate VxWorks position independent code >> -non_shared do not generate code that can operate with DSOs >> -xgot assume a 32 bit GOT >> >> Just to make things fun, the SGI notion of cpic (call pic) fits gnu's -cal...
2016 Dec 13
3
Enabling statistics in release builds / static constructors
...time to build an auto-registration system that doesn't involve static constructors? I would volunteer to do the work, however this obviously needs some consensus first on how that would look. > > It needs custom code for every supported object file format, and is hard to get right when DSOs are involved, but in the long run it's probably worth fixing this problem once and for all. I assume you are thinking about creating custom linker sections with list of init functions; Similar to the existing constructors sections but running at a time controlled by llvm code. While the compile...
2018 Feb 07
0
ThinLTO and linkonce_odr + unnamed_addr
...pting MachO into -fvisibility-inlines-hidden all the time, i.e. if the function is linkonce, it's discardable, so mark it hidden to pretend the compiler inlined it and discarded it. However, this isn't conforming, because the addresses of inline functions will no longer compare equal across DSOs. Realistically, nobody cares about this guarantee. Maybe we should enable -fvisibility-inlines-hidden by default to resolve this inconsistency between the platforms. It's a much better out of the box experience anyway. On Wed, Feb 7, 2018 at 11:11 AM, Steven Wu <stevenwu at apple.com> w...
2014 Jul 05
2
[LLVMdev] [lld] [mach-o]: RFC: representing LC_REEXPORT_DYLIB
On Wed, Jul 02, 2014 at 05:09:14PM -0700, Nick Kledzik wrote: > Shankar, Does lld for ELF support loading indirect DSOs? It doesn't, which is a bug. Joerg
2016 Dec 27
2
Bootstrapping with in-tree libcxx
...e system. Since building all of llvm required CXX and using libcxx with the same version as the rest of llvm makes sense, I would certainly appreciate an option to build the in-tree libcxx as a first step and use it in when building llvm, lld, lldb, clang, ... Since llvm already builds many other DSOs it needs at runtime, adding libcxx is reasonable. More so if we consider that not all systems package libcxx at the same version as clang and llvm. For instance, Arch Linux has libcxx 3.8.0 but llvm and clang 3.9.0.
2002 Sep 13
1
[LLVMdev] Linux-x86 Compatibility
ISSUE: DSOs in Linux are created by "g++ -shared" instead of "g++ -G". ACTION: Compile with "g++ -shared" instead of "g++ -G", i.e., use the alternate definition of "MakeSO" in Makefile.common. PATCH: Apply from llvm top-level directory with "patch -p0&...
2017 Dec 11
2
[lld] bug detecting undefined symbols in shared libraries
I have a test case where lld-5.0 fails to detect an undefined symbol (this bug also happens with clang/lld 4.0). I haven't narrowed down exactly all the circumstances when this can occur, but in this case it was for a virtual method in a class defined in a shared library. If I build the executable with the raw object files, the linker notices the missing method (see test1 vs test2). This