similar to: [LLVMdev] Instruction.def not installed any more?

Cool, I'll check it out - thanks! On Wed, Jun 29, 2011 at 12:07 AM, Eli Friedman <eli.friedman at gmail.com>wrote: > On Mon, Jun 27, 2011 at 6:32 PM, Eli Friedman <eli.friedman at gmail.com> > wrote: > > On Sat, Jun 25, 2011 at 1:34 AM, Eli Friedman <eli.friedman at gmail.com> > wrote: > >> On Fri, Jun 24, 2011 at 10:51 PM, Talin <viridia at

So this was working fine for me until a few days ago when I checked out the most recent LLVM - the one with the new type system. Now I am getting the same error that I was getting previously. Is it possible that your fix got unfixed when they merged in the new branch? On Thu, Jun 30, 2011 at 2:21 PM, Talin <viridia at gmail.com> wrote: > Cool, I'll check it out - thanks! > >

On Sat, Jun 25, 2011 at 1:34 AM, Eli Friedman <eli.friedman at gmail.com> wrote: > On Fri, Jun 24, 2011 at 10:51 PM, Talin <viridia at gmail.com> wrote: >> A couple of months ago, I started the process of updating my CMake scripts >> to allow my compiler to be compiled with clang. I quickly ran into a problem >> calling the LLVM libraries, which is that I would get

A couple of months ago, I started the process of updating my CMake scripts to allow my compiler to be compiled with clang. I quickly ran into a problem calling the LLVM libraries, which is that I would get segfaults when calling LLVM API functions. I posted about this on both the clang and llvm-dev lists, but there was no response, so I decided to put the clang-related work on hold. Last week I

On Mon, Jun 27, 2011 at 6:32 PM, Eli Friedman <eli.friedman at gmail.com> wrote: > On Sat, Jun 25, 2011 at 1:34 AM, Eli Friedman <eli.friedman at gmail.com> wrote: >> On Fri, Jun 24, 2011 at 10:51 PM, Talin <viridia at gmail.com> wrote: >>> A couple of months ago, I started the process of updating my CMake scripts >>> to allow my compiler to be compiled

On Fri, Jun 24, 2011 at 10:51 PM, Talin <viridia at gmail.com> wrote: > A couple of months ago, I started the process of updating my CMake scripts > to allow my compiler to be compiled with clang. I quickly ran into a problem > calling the LLVM libraries, which is that I would get segfaults when calling > LLVM API functions. I posted about this on both the clang and llvm-dev >

Hi Talin, This looks interesting..! Can you email me your tool? Cheers, Raghu. ----- Original Message ----- From: "Renato Golin" <rengolin at systemcall.org> To: "Talin" <viridia at gmail.com> Cc: "LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu> Sent: Saturday, February 12, 2011 1:31:10 AM Subject: Re: [LLVMdev] Introducing LLBrowse: A

On Sun, Oct 10, 2010 at 9:54 AM, Talin <viridia at gmail.com> wrote: > BTW, the reason I stopped responding to this thread is not because I solved > the problem, but because I simply gave up and decided to work on other > things for a while since I was making no progress. Having finished those > other things (the stack crawler, for one), I'm hoping that time and a fresh >

Nice! I'm interested... would also be nice to cross this with llvm diff, eh? :) Cheers, Renato On 12-Feb-2011 7:28 AM, "Talin" <viridia at gmail.com> wrote: > I've written a little GUI application that displays an LLVM module as an > expandable tree, which can be useful for examining the module's contents. > Some features: > > - Based on wxWidgets, so

LLBrowse has now been checked in to the llvm.org subversion repository: http://llvm.org/svn/llvm-project/llbrowse/trunk/ There are instructions for building and running in the doc/ directory. <http://llvm.org/svn/llvm-project/llbrowse/trunk/>First task if someone wants to take it on - update all of the source files to have the UIUC license info at the top, and add a LICENSE.txt file :)

BTW, the reason I stopped responding to this thread is not because I solved the problem, but because I simply gave up and decided to work on other things for a while since I was making no progress. Having finished those other things (the stack crawler, for one), I'm hoping that time and a fresh start will yield better results. Unfortunately after about a day spent reviewing old llvm-dev

OK I figured out what the problem was - I assume you are trying to compile under Snow Leopard? There is a problem with linking against wxWidgets because the prebuilt binaries for wxWidgets are compiled in 32-bit mode, and the default compilation mode in Snow Leopard is 64 bits. See this article for an explanation: http://wiki.wxwidgets.org/Development:_wxMac#Building_under_10.6_Snow_Leopard

On Sat, Oct 15, 2011 at 9:49 PM, Chandler Carruth <chandlerc at google.com>wrote: > On Sat, Oct 15, 2011 at 9:20 PM, Talin <viridia at gmail.com> wrote: > >> I recently updated my version of LLVM from revision 140108 to 142082, and >> several things broke, most of which were easily fixed. However, I'm now >> getting a "pure virtual method called"

On Sat, Aug 28, 2010 at 4:05 PM, Talin <viridia at gmail.com> wrote: > On Mon, Aug 23, 2010 at 5:58 PM, Devang Patel <devang.patel at gmail.com>wrote: > >> >> On Sun, Aug 22, 2010 at 12:50 PM, Talin <viridia at gmail.com> wrote: >> >>> I recently started getting this error when I try to debug my >>> LLVM-compiled program in GDB:

On Mon, Aug 23, 2010 at 5:58 PM, Devang Patel <devang.patel at gmail.com>wrote: > > On Sun, Aug 22, 2010 at 12:50 PM, Talin <viridia at gmail.com> wrote: > >> I recently started getting this error when I try to debug my LLVM-compiled >> program in GDB: >> >> Dwarf Error: Cannot find DIE at 0x16769 referenced from DIE at 0x1713c >> [in module

On Sat, Jul 23, 2011 at 5:09 PM, Talin <viridia at gmail.com> wrote: > So this was working fine for me until a few days ago when I checked out the > most recent LLVM - the one with the new type system. Now I am getting the > same error that I was getting previously. > Is it possible that your fix got unfixed when they merged in the new branch? I wouldn't be surprised if

I've written a little GUI application that displays an LLVM module as an expandable tree, which can be useful for examining the module's contents. Some features: - Based on wxWidgets, so it's completely cross-platform. - CMake build script can locate both LLVM and wxWidgets installations automatically. - Loads either .ll or .bc files. - Supports browsing of LLVM types,

Interestingly, I also get a similar error in a different executable (my unittest): pure virtual method called terminate called without an active exception 0 tartc 0x00000001010a8265 PrintStackTrace(void*) + 53 1 tartc 0x00000001010a88cc SignalHandler(int) + 364 2 libSystem.B.dylib 0x00007fff831341ba _sigtramp + 26 3 libSystem.B.dylib 0x7261742e65637365 _sigtramp +

Sorry, I meant DIBuilder. On Fri, Feb 18, 2011 at 1:32 PM, Talin <viridia at gmail.com> wrote: > I didn't know DIFactory existed until you mentioned it just now. > > And if folks are adding brand new classes to LLVM, can we not follow the > naming conventions in the developer guidelines? > > On Fri, Feb 18, 2011 at 5:14 AM, Renato Golin <rengolin at

LLBrowse - a GUI tool which allows you to inspect the contents of LLVM modules - now runs on Linux and OS X, and it works with both LLVM 2.8 and current LLVM head. I've updated the docs to include instructions on checking out and building the code under several different environments, which you can read here: http://llvm.org/svn/llvm-project/llbrowse/trunk/doc/LLBrowse.html (the doc also