Closed GoogleCodeExporter closed 9 years ago
I'm trying to fix this, by now I found two changes on LLVM head that breaks
llvm-py:
see:
svn diff -r 52834 ./include/llvm/Module.h
svn diff -r 52523 ./include/llvm-c/ExecutionEngine.h
agains LLVM HEAD (the first change relates to my original comment, the second
will
only appear if you fix the first).
Original comment by ph.silva
on 18 Sep 2008 at 8:49
Follow a very very bad patch: It actually makes llmv-py build against LLVM head
BUT
needs more changes to be a final one. Please don't commit it :) Just to feed the
discussions. Also follow the relevant revisions where most things changed on
LLVM
that affects current llvm-py (just to make things easier to follow)
svn diff -r 52834 ./include/llvm/Module.h
svn diff -r 52523 ./include/llvm-c/ExecutionEngine.h
svn diff -r 53950 ./include/llvm/Support/IRBuilder.h
svn diff -r 53931 ./include/llvm/Support/IRBuilder.h
svn log -r r54822 ./include/llvm/Transforms/Scalar.h
Original comment by ph.silva
on 18 Sep 2008 at 11:42
Attachments:
Sorry for the late reply.
Please see this:
http://mdevan.nfshost.com/llvm-py/userguide.html#llvm24
Original comment by mdevan.f...@gmail.com
on 24 Sep 2008 at 11:16
Alright, stupid me, sorry about that, I didn't saw that page before, just close
this
bug, that's OK for me :) great work. Was a nice way to learn how to track LLVM
API
changes anyway.
Original comment by ph.silva
on 24 Sep 2008 at 11:40
Do you have roadmap related to track next October 2.4 release of LLVM? Maybe do
a
simultaneous release, would be great! I'll fetch the llpy-py 2.4 branch and
test the
way I could here.
Original comment by ph.silva
on 24 Sep 2008 at 11:43
Well, there's no roadmap. I'll naturally be attempting to make a release as
soon as
LLVM 2.4 is done.
Closing.
Original comment by mdevan.f...@gmail.com
on 26 Sep 2008 at 5:00
Original comment by mdevan.f...@gmail.com
on 26 Sep 2008 at 5:00
Original issue reported on code.google.com by
ph.silva
on 18 Sep 2008 at 8:13