search for: relinked

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:

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

On Oct 23, 2007, at 18:19, BGB wrote: > On Oct 23, 2007, at 11:45, Gordon Henriksen wrote: > >> Generally speaking, LLVM neither helps nor hinders here. Maybe >> someone will follow up with whether the JIT uses stub functions >> which would enable dynamic relinking If not, it would be a >> straightforward, if platform-specific, feature to add. > > I

/bin/sh ../../mkinstalldirs /sw/lib/xmms/Input ../../libtool-disable-static --mode=install /usr/bin/install -c libxmms-flac.la /sw/lib/xmms/Input/libxmms-flac.la libtool-disable-static: install: warning: relinking `libxmms-flac.la' cd /Users/glenn/Desktop/flac-1.0.5_beta1/src/plugin_xmms; /bin/sh ../../libtool-disable-static --mode=relink gcc -I../.. -I./include -I../../include -g -O2

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

I'm making a Fink package for FLAC. It all builds fine except for the xmms plugin. I'd use the pbproject, but fink users are likely to want the xmms plugin which pbxbuild does not build. Also it seems the pbproject does not build dynamic libraries. I build with: ./configure --prefix=/sw --mandir=/sw/share/man make make install DESTDIR=/tmp (to simulate building into a deb file) The

...his would probably one-off the function, by forcibly relinking it as a proxy to the function (any future attempts at relinking the function then simply adjust its associated pointer). potentially, this could also be made the default behavior for when relinking functions (if they are being forcibly relinked, well, assume they are being made movable). or such... ccMakeMovable(char *func); //an explicit call to the VM __movable void foo(int x) { //do something... } even more interestingly: if the same compiler were also used for static compilation, it could be used as a special feature to m...

Hi, I'm trying to transition from the JIT to MCJIT. The requirements are fast response time and dynamic unloading/replacement of modified functions. Lazy evaluation is *not* required: I expect all functions to be present at runtime or else an error is fine. With the JIT it's quite simple to unload and replace functions due to the stubs (JMP instructions) that redirect the actual function

----- Original Message ----- From: "Gordon Henriksen" <gordonhenriksen at mac.com> To: "LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu> Sent: Wednesday, October 24, 2007 1:45 AM Subject: Re: [LLVMdev] me being stupid: me vs the llvm codebase... On Oct 23, 2007, at 05:52, BGB wrote: > I am assuming then that some external assembler is used (such as >

Hi, Let's suppose we have an ELF executable that doesn't issue any syscall (I mean, syscalls are issued from an external dynamic library, not from the executable, and we can ignore such dynamic library because we have the proper equivalent library with the proper syscalls in MacOS and Windows). So, the question: Is it "currently possible" (by "currently possible" I

LLVM, When we recompile, is it possible to "make" only one of the tools, or at least relink only the tools whose object files have changed? Thanks Dave

Sure, that makes a lot of sense. The implementation details may get tricky, of course, but the concept is great. -Jim On Oct 30, 2013, at 12:20 PM, Yaron Keren <yaron.keren at gmail.com> wrote: > Hi, > > I'm trying to transition from the JIT to MCJIT. The requirements are fast response time and dynamic unloading/replacement of modified functions. Lazy evaluation is *not*

--- Ben Hines <bhines@alumni.ucsd.edu> wrote: > I guess the problem is really why is it trying to relink it? > > The "parse error: condition expected:" is suspicious, though.. maybe > it's another "zsh as sh" problem... hmm.. I don't remember having any trouble building the plugin on my ibook but that was a few months ago, so my memory may be fuzzy.

Hi Charllls, I didn't really get it. Are you saying that you would execute some functions using the JIT then, later, those functions will be modified and thus need to be re-jitted? Ciao, Duncan. On 07/06/12 20:13, Charllls Alquarra wrote: > > Sorry if it comes out a bit pushy bumping my own question, but it's been really > difficult to find any info regarding this functionality

> De: Duncan Sands <baldrick at free.fr> >Para: >Enviado: miércoles, 11 de julio de 2012 9:40 >Asunto: Re: [LLVMdev] dynamic linkage for jit > >Hi Charllls, I didn't really get it. Are you saying that you would execute some >functions using the JIT then, later, those functions will be modified and thus >need to be re-jitted? > >Ciao, Duncan. Hi Duncan,

Ok, it seems i had problems with stale stuff in there. I made clean and started over. The first part now correctly says " remember to run `libtool --finish /sw/lib'". The xmms plugin now gives a different error: /bin/sh ../../mkinstalldirs /tmp/sw/lib/xmms/Input ../../libtool-disable-static --mode=install /usr/bin/install -c libxmms-flac.la

--- Ben Hines <bhines@alumni.ucsd.edu> wrote: > At 10:39 AM -0700 5/21/02, Josh Coalson wrote: > >--- Ben Hines <bhines@alumni.ucsd.edu> wrote: > >> I guess the problem is really why is it trying to relink it? > >> > >> The "parse error: condition expected:" is suspicious, though.. > maybe > >> it's another "zsh as

The new MCJIT is module-oriented, like a classic compiler+linker (which it is) while the old JIT is function-oriented. If I understand correctly, the main problems with the old JIT were the duplication of the debug information code and EH code (both gone now). Moreover, if we ignore the lazy evaluation mechanism then the current JIT is actually quite simple module. Would it be possible to keep

I'm trying to get R running on OpenBSD/alpha. I've applied some configure patches which I've previously sent to the R-devel list to allow R to compile on an OpenBSD ELF platform (which OpenBSD/alpha is, as the i386 port soon will be). The patched source compiles without problems, and appears to run and perform properly apart from two (possibly unrelated) problems. 1) On startup

Hi, JIT does not allow functions to call others in different modules, so all modules need to be statically linked in a big fat module. If a module needs to be recompiled, all the others need to as well as relinked. there are two ways i intend to approach this problem: 1) forget about JITing, build each module into a .bc, call gcc to generate .soname libraries, dynamically load with dlopen() those libraries 2) keep the modules unlinked, and when execution is required, link the required dependencies into an...