Hi, Does any interactive llvm interpreter exist or is there one being developed at the moment? What I am talking about is something like LLI but interactive so that it is possible to step through LLVM code statement by statement and inspect the results of various expressions. This would for example greatly simplify debugging of compiler passes. We are thinking of having a master's student work on that as a master's thesis project, but it would be good to know whether that would be duplicating anyone else's current ongoing work. Kind regards, Mattias
On Mar 5, 2009, at 8:54 AM, Mattias Holm wrote:> Hi, > > Does any interactive llvm interpreter exist or is there one being > developed at the moment? What I am talking about is something like LLI > but interactive so that it is possible to step through LLVM code > statement by statement and inspect the results of various expressions. > This would for example greatly simplify debugging of compiler passes. > > We are thinking of having a master's student work on that as a > master's thesis project, but it would be good to know whether that > would be duplicating anyone else's current ongoing work.I don't know of anything like that. One implementation approach would be to insert debug information into a .ll file based on the location information of the .ll file itself. That would allow you to compile the code normally and step through "the .ll file" in GDB. -Chris
On Thursday 05 March 2009 17:50:31 Chris Lattner wrote:> On Mar 5, 2009, at 8:54 AM, Mattias Holm wrote: > > Does any interactive llvm interpreter exist or is there one being > > developed at the moment? What I am talking about is something like LLI > > but interactive so that it is possible to step through LLVM code > > statement by statement and inspect the results of various expressions. > > This would for example greatly simplify debugging of compiler passes. > > I don't know of anything like that. One implementation approach would > be to insert debug information into a .ll file based on the location > information of the .ll file itself. That would allow you to compile > the code normally and step through "the .ll file" in GDB.I think a walkthrough of the source, like the Kaleidoscope tutorials, would also be extremely valuable. -- Dr Jon Harrop, Flying Frog Consultancy Ltd. http://www.ffconsultancy.com/?e