[llvm-dev] Getting the original high-level code

marwayusuf@feng.bu.edu.eg via llvm-dev llvm-dev at lists.llvm.org
Wed Mar 16 06:16:01 PDT 2016


Thanks a million!


Regards,
Marwa Yusuf
Teaching Assistant - Computer Engineering Department
Faculty of Engineering - Benha University
E-JUST PhD Student
Computer Science & Engineering Dept.


________________________________
From: Lang Hames <lhames at gmail.com>
Sent: Wednesday, March 16, 2016 2:15 AM
To: David Blaikie
Cc: marwayusuf at feng.bu.edu.eg; llvm-dev at lists.llvm.org
Subject: Re: [llvm-dev] Getting the original high-level code

Hi Marwa,

There's no generic way to de-compile IR, but if the IR has debug info attached you may be able to find the path to the original source file.

- Lang.

On Tue, Mar 15, 2016 at 10:43 AM, David Blaikie via llvm-dev <llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>> wrote:
There's nothing built into LLVM and Clang for going backwards through the lowering chain (MC->IR, IR->C++, etc). I think some third parties have built some pieces of this, but of course it is rather lossy.

On Tue, Mar 15, 2016 at 6:22 AM, marwayusuf at feng.bu.edu.eg<mailto:marwayusuf at feng.bu.edu.eg> via llvm-dev <llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>> wrote:

Dear All

Is there is a way I can get the original hogh level code (e.g c++ code) of an IR function within MCJIT?


Regards,
Marwa Yusuf
Teaching Assistant - Computer Engineering Department
Faculty of Engineering - Benha University
E-JUST PhD Student
Computer Science & Engineering Dept.

_______________________________________________
LLVM Developers mailing list
llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev



_______________________________________________
LLVM Developers mailing list
llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160316/778b4437/attachment.html>


More information about the llvm-dev mailing list