similar to: Relinking (syscall-free) ELF executable into Mach-O and PE executables

Couldn’t you write the relocations to the ELF executable? I don’t know if current linkers have support for this, but it seems possible in theory to make a relinkable executable. If you want to do this with an already linked executable though, then yea this won’t be possible. On Fri, Jul 20, 2018 at 10:30 AM Reid Kleckner via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Typically

Hi, I'm looking for some sort of "universal loader and dynamic linker", capable of loading in memory an executable (ELF or other, the format is not a requisite at this time) for any of the "major" architectures that have LLVM backends (namely: x86, x86_64, ARM, ARM64, PPC, PPC64, MIPS32, MIPS64), including also relocation, and loading of symbols from dynamic libraries that

On 4/3/2018 9:33 AM, ardi via llvm-dev wrote: > Hi, > > I'm looking for some sort of "universal loader and dynamic linker", > capable of loading in memory an executable (ELF or other, the format > is not a requisite at this time) for any of the "major" architectures > that have LLVM backends (namely: x86, x86_64, ARM, ARM64, PPC, PPC64, > MIPS32,

Hi Assuming I had an application stub based on (say) lli, and I'd like to allow a hypothetical IDE to recompile and relink a function: Is that supported in any way currently? Assuming actually patching all call sites to point to the newly generated function is possible, I guess what I need is to be able to either track or find all of the call sites. The trickiest bit seems to be if the

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

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

Hi everyone, I''ve been running a zfs fileserver for about a month now (on snv_91) and it''s all working really well. I''m scrubbing once a week and nothing has come up as a problem yet. I''m a little worried as I''ve just noticed these messages in /var/adm/message and I don''t know if they''re bad or just informational: Aug 2 14:46:06

On 4/15/16, Joerg Sonnenberger via llvm-dev <llvm-dev at lists.llvm.org> wrote: > On Fri, Apr 15, 2016 at 02:31:59PM +0200, ardi via llvm-dev wrote: >> On Fri, Apr 15, 2016 at 1:02 PM, Joerg Sonnenberger via llvm-dev >> <llvm-dev at lists.llvm.org> wrote: >> > On Fri, Apr 15, 2016 at 10:45:03AM +0200, ardi via llvm-dev wrote: >> >> What I found is

Thanks a lot, but tried it and I get this: CMake Error at projects/libcxx/CMakeLists.txt:361 (message): LIBCXX_ENABLE_STATIC_ABI_LIBRARY is not supported on OS X Why is it not supported? If I manually embed libc++abi.a inside libc++.a it seems to work. Thanks! ardi On Mon, Oct 1, 2018 at 4:20 AM Petr Hosek <phosek at chromium.org> wrote: > > You can use

On Fri, Apr 15, 2016 at 1:02 PM, Joerg Sonnenberger via llvm-dev <llvm-dev at lists.llvm.org> wrote: > On Fri, Apr 15, 2016 at 10:45:03AM +0200, ardi via llvm-dev wrote: >> What I found is that the build system is really complex, performs many >> checks, and quite often takes wrong decisions (example: a fatal error >> if the OS X version is older than 10.7, instead of

From: "Xiaowei.Hu" <xiaowei.hu at oracle.com> ocfs2_block_group_alloc_discontig() disables chain relink by setting ac->ac_allow_chain_relink = 0 because it grabs clusters from multiple cluster groups. It doesn't keep the credits for all chain relink,but ocfs2_claim_suballoc_bits overrides this in this call trace:

Habe Samba 2.2.3a unter HP-UX 10.20 laufen. (letzte Version die ich f?r 10.20 finden konnte) Bisher lief alles bestens. Jetzt mu? ich XP Prof einbinden. Geht ja, aber bei mehreren Programmen (z.B. Office 2003) st?rzt das Programm beim Speichern ab. Geht das grunds?tzlich mit einer so alten Version nicht oder gibt es einen Workaround? Danke Andi

Looking at tools/clang/lib/Driver/Tools.cpp , there's this fragment of code: if (Args.hasArg(options::OPT_rdynamic) && Version[0] >= 137) CmdArgs.push_back("-export_dynamic"); I built LLVM 3.4.2 from a OS X 10.11 "El Capitan" but specifying a fat build (386+x86_64) and requesting support back up to 10.6. It went fine, and the build passes all tests when run

Hi! I sometimes build LLVM with a static libc++.a in MacOS, so that I use the LLVM libc++ instead of the system-wide one. However, when doing so, I always get link errors when building LLVM, because the build system links with libc++.a, but not with libc++abi.a and so there are quite a few missing symbols that the linker cannot find. My workaround (which always seems to work) is to embed

Hello, I would like to connect jabber client (Exodus) to Asterisk 1.4. Asterisk 1.4 already supported jabber (client/component), didn't it? Can I connect Exodus to Asterisk directly? And if yes, please tell me how to connect? Kawamoto -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi, I'd like to experiment with the MIPS and PowerPC backends, but, considering that they aren't widely used processors, I'd like to start with the same environment (OS/ABI/linker) used by the people who work with these backends. So, what OS/ABI/linker use the people who use these backends for production work? Thanks!!

Hi, I don't know if there's a wishlist for future LLVM releases but, in case there is one, maybe you'd like to consider my experience (as a multiplatform application developer who discovered clang just because Apple started to include it in Xcode since 10.8 Mountain Lion IIRC, and really liked it, specially for how warnings are issued, which really helps to improve your app code

Using control_work instead of config_work as the 3rd argument to container_of results in an invalid portdev pointer. Indeed, the work structure is initialized as below: INIT_WORK(&portdev->config_work, &config_work_handler); It leads to a crash when portdev->vdev is dereferenced later. This bug is triggered when the guest uses a virtio-console without multiport feature and

Using control_work instead of config_work as the 3rd argument to container_of results in an invalid portdev pointer. Indeed, the work structure is initialized as below: INIT_WORK(&portdev->config_work, &config_work_handler); It leads to a crash when portdev->vdev is dereferenced later. This bug is triggered when the guest uses a virtio-console without multiport feature and

Is the MIPS backend production-ready for any (or all) of the OSs you mention? As I said, I'd like to start using the MIPS and PowerPC backends with an OS/linker where they are most reliable. In the case of PowerPC, from the comments I conclude there's people successfully using the backend in Linux. OTOH, FreeBSD is "almost there", and not sure about NetBSD and OpenBSD. In the