search for: r266158

...and assigned to me by my request. As I learned as I implemented more and more of lld, the actual application of relocations is small part of the linker interaction. A big part is deciding about relaxations, copy relocations, gots and plts, so I rewrote the relocation handling in its current form (r266158). That involves saving information during the first of two passes over the relocations. I really don't think that that is what the JIT wants. > Now maybe the JIT's linking functionality should be so different from > what LLD does that there's no overlap, but I think that a lot of...

On Mon, Dec 12, 2016 at 8:13 AM, Rafael Avila de Espindola via llvm-dev < llvm-dev at lists.llvm.org> wrote: > David Chisnall via llvm-dev <llvm-dev at lists.llvm.org> writes: > > > On 12 Dec 2016, at 03:39, Rui Ueyama via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> > >> LLD's driver currently takes only a command line argument

----- Original Message ----- > From: "Rafael Avila de Espindola" <rafael.espindola at gmail.com> > To: "Hal Finkel" <hfinkel at anl.gov>, "Rui Ueyama" <ruiu at google.com> > Cc: "llvm-dev" <llvm-dev at lists.llvm.org> > Sent: Tuesday, December 13, 2016 2:13:49 PM > Subject: Re: [llvm-dev] LLD status update and