(original) (raw)
Not yet unfortunately. I've had my head down working on a jut-linker replacement.
Let me take a look right now...
On Mon, Feb 18, 2019 at 10:40 AM David Blaikie <dblaikie@gmail.com> wrote:
Ping - did this end up getting addressed?On Mon, Jan 21, 2019, 6:15 PM Lang Hames <lhames@gmail.com wrote:Hi Nick,I was not aware of it, but it makes sense given the recent switch to ORC2, which has different symbol resolution rules.I am out on vacation this week, but will take a look when I get back and see if I can restore the old behavior.Cheers,Lang.Sent from my iPhone+Lang who does JIT things
Yeah, I can confirm my local build (using LLVM source from today) of Chapter 4 behaves as you describe, and not as the documentation shows. Looks like somethnig needs updating (either source or the documentation).On Sun, Dec 30, 2018 at 3:28 PM Nick Desaulniers via llvm-dev <llvm-dev@lists.llvm.org> wrote:https://llvm.org/docs/tutorial/LangImpl04.html has an example where
the function \`foo\` gets redefined, and the JIT returns evaluation of
the latest definition. I thought my code was wrong, but it seems that
the binary produced by \`ninja Kaleidoscope-Ch4\` has the same bug.
Granted, my LLVM checkout is from Nov 3 2018 (r346062). Is this a known issue?
\~Nick Desaulniers
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
LLVM Developers mailing list
llvm-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev