Displaying 7 results from an estimated 7 matches for "mach_o".
Did you mean:
mach_io
2011 Sep 02
1
[LLVMdev] does new EH require newer linker?
...gcc -lSystem /sw/lib/gcc4.6/lib/gcc/x86_64-apple-darwin11.0.0/4.6.1/crtfastmath.o
Reading symbols for shared libraries ++......................... done
Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_INVALID_ADDRESS at address: 0x0000000000000028
0x00000001000159b9 in mach_o::relocatable::Section<x86_64>::addRelocFixup ()
(gdb) bt
#0 0x00000001000159b9 in mach_o::relocatable::Section<x86_64>::addRelocFixup ()
#1 0x0000000100047a4c in mach_o::relocatable::Section<x86_64>::makeFixups ()
#2 0x00000001000437a3 in mach_o::relocatable::Parser<x86_64&g...
2019 Apr 08
2
LLVM 8 + Mavericks?
...fd68
llvm::sys::RunSignalHandlers() + 248
2 ld 0x000000010e7412e8 SignalHandler(int) + 264
3 libsystem_platform.dylib 0x00007fff8cc005aa _sigtramp + 26
4 libsystem_platform.dylib 0x00007fff5156f6e8 _sigtramp + 3298226520
5 ld 0x000000010e977ad5
lld::mach_o::MachODylibFile::exports(llvm::StringRef, llvm::StringRef)
const + 53
6 ld 0x000000010e977b5a
lld::mach_o::MachODylibFile::exports(llvm::StringRef, llvm::StringRef)
const + 186
7 ld 0x000000010e977b5a
lld::mach_o::MachODylibFile::exports(llvm::Strin...
2016 Sep 12
2
lld: add build-time control for including ELF / COFF / Mach-O linkers?
On 12 September 2016 at 16:23, Rui Ueyama <ruiu at google.com> wrote:
> What's the motivation to not build COFF and Mach-O parts? If you don't need
> it, you could just leave it. Are you trying to reduce the executable size?
It was just easier to remove coff::link() and mach_o::link() from
lld.cpp than to add them to our own build infrastructure
https://svnweb.freebsd.org/base/projects/clang390-import/usr.bin/clang/lld/Makefile?view=markup
We get a slightly faster build and a slightly smaller binary, but I
was motivated more by laziness than those factors. That is, it w...
2016 Dec 14
0
LLD status update and performance chart
...if it can self-host yet.
>
> 3. Is there anything preventing "main() in a library" from supporting all
> of these platforms and architectures?
>
>
All 3 already provide this. If you look in main() in lld/tools/lld/lld.cpp
you can see the corresponding calls to {elf,coff,mach_o}::link. There are
some caveats for ELF and especially COFF. Basically, the ELF and COFF ones
are not re-entrant currently, and the COFF one currently uses fatal error
handling for common errors (ELF did too, but a user requested that it not
do so and it was fixed).
-- Sean Silva
-------------- nex...
2016 Sep 12
2
lld: add build-time control for including ELF / COFF / Mach-O linkers?
We're in the process of importing lld into FreeBSD (along with our
Clang 3.9 update project). For now I've removed all but the ELF
linker[1]. We have no need for COFF and Mach-O, and we have a bespoke
build system for all of our contrib code. I didn't bother adding build
support for the source files for non-ELF linkers.
Is this something that'd be reasonable / desirable to have
2016 Dec 14
2
LLD status update and performance chart
On Tue, Dec 13, 2016 at 10:59 PM, Sean Silva via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
>
> Yes. Rui has bent over backwards every time a real user has come to us and
> said "we need X". The historical precedent here is that LLD is open to many
> kinds of changes, but not on theoretical grounds.
>
> Admittedly this leads to a somewhat conservative design