I tried compiling latest llvm with clang (3.3). I am trying to generate c++ API code from bitcode(.bc) file using "llc -march=cpp" This used to work with 2.3 release (I guess). With the current release, it is unable to figure out architecture "cpp" am doing something wrong? is there other way to achieve this? may be different utility that I missed? --Ashish -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130225/98a80bc9/attachment.html>
Hi Ashish,> This used to work with 2.3 release (I guess). > With the current release, it is unable to figure out architecture "cpp"That's a big gap! Regardless, it should still work exactly as you're trying to do. It does on my local builds.> am doing something wrong? is there other way to achieve this?Could you tell us how you're building LLVM? (I.e. cmake or configure command-line). It's possible you're disabling the cpp backend without realising it. Of course, it's also worth trying a completely fresh build directory and making sure you don't give any suspicious arguments to the build system. Especially if your current directory is a hold-over from some build of version 2.3. Goodness knows what's happened in that time. Cheers. Tim.
I took the latest llvm code using svn. Then check out the clang at its usual location. Then created "build" directory. After that I issued "cmake /path/to/llvm/root" from inside "build" diectory. After that I just hit "make" I think, cmake is doing some stuff behind my back. I will try to compile using configure script. --Ashish On 25 Feb 2013, at 19:18, Tim Northover <t.p.northover at gmail.com> wrote:> Hi Ashish, > >> This used to work with 2.3 release (I guess). >> With the current release, it is unable to figure out architecture "cpp" > > That's a big gap! Regardless, it should still work exactly as you're > trying to do. It does on my local builds. > >> am doing something wrong? is there other way to achieve this? > > Could you tell us how you're building LLVM? (I.e. cmake or configure > command-line). It's possible you're disabling the cpp backend without > realising it. > > Of course, it's also worth trying a completely fresh build directory > and making sure you don't give any suspicious arguments to the build > system. Especially if your current directory is a hold-over from some > build of version 2.3. Goodness knows what's happened in that time. > > Cheers. > > Tim.