similar to: [LLVMdev] Demangling question

Below is an example of using backtrace() obtained from man backtrace and the test results: $ gcc bt.c -o bt-gcc $ ./bt-gcc 4 backtrace() returned 4 addresses ./bt-gcc() [0x4007e3] ./bt-gcc() [0x400874] ./bt-gcc() [0x40089b] ./bt-gcc() [0x400894] $ llvm-gcc bt.c -o bt-llvm-gcc $ ./bt-llvm-gcc 4 backtrace() returned 4 addresses ./bt-llvm-gcc() [0x40074b] ./bt-llvm-gcc() [0x400809]

I'm hoping to revive the LLD standalone CMake build. I'm new to this build but it looks like it borrowed code from an old version of compiler-rt, which I did some work on last year. Like compiler-rt, I'd like to get the LLD build up running with only CMAKE_PREFIX_PATH instead of defining custom variables like LLD_PATH_TO_LLVM_BUILD and LLD_PATH_TO_LLVM_SOURCE. Any objection to that?

This looks relevant to me for your issue. Grabbing the cxxabi.h from there may work: http://comments.gmane.org/gmane.comp.compilers.clang.devel/9391 -- Aaron Myles Landwehr On Sat, Jul 30, 2011 at 1:33 AM, 陳韋任 <chenwj at iis.sinica.edu.tw> wrote: > Hi, all > > I am trying to selfhost LLVM and Clang. Below is my flow, > > Step 1. Build LLVM and Clang by using native gcc

Attempting to build llvm on Mageia2 from the 3.3 source I get: "#include "..." search starts here: #include <...> search starts here: /home/mgeldiener/dev/clang/build/include /home/mgeldiener/dev/clang/build/lib/Support /home/mgeldiener/vcs/llvm/include /home/mgeldiener/vcs/llvm/lib/Support /opt/intel/composerxe-2011.5.220/mkl/include

I really want to start simple. So if adding a demangler the first objective is to add one that lets us drop the HAVE_CXXABI_H. After that it can be expanded. Cheers, Rafael On 5 May 2016 at 08:58, David Chisnall <David.Chisnall at cl.cam.ac.uk> wrote: > On 5 May 2016, at 13:47, Rafael Espíndola via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> >> * Is having an

How do you feel about adding LLD to the LLVM repo? Could it follow the same path as the integrated assembler? That is, Clang keeps it off by default for each architecture until it's ready for prime time. -Greg On Thu, Jan 8, 2015 at 3:31 PM, Sean Silva <chisophugis at gmail.com> wrote: > > > On Wed, Jan 7, 2015 at 6:38 PM, Greg Fitzgerald <garious at gmail.com> wrote:

Hi, all I am trying to selfhost LLVM and Clang. Below is my flow, Step 1. Build LLVM and Clang by using native gcc $ ../llvm-2.9/configure --prefix=$INSTALL \ --enable-optimized Step 2. Build LLVM and Clang by using clang built by step 1 $ CC=clang CXX=clang++ ../llvm-2.9/configure \ --prefix=$INSTALL --enable-optimized But in step 2, I have a compilation error below, -- llvm[1]:

Hi, Asron > This looks relevant to me for your issue. Grabbing the cxxabi.h from there > may work: > > http://comments.gmane.org/gmane.comp.compilers.clang.devel/9391 I am not sure where to put cxxabi.h. How can I let clang find this header file while compiling LLVM and Clang (in step 2)? Thanks! Regards, chenwj -- Wei-Ren Chen (陳韋任) Computer Systems Lab, Institute of

On 01/06/2013 07:20 PM, Dmitri Gribenko wrote: > On Mon, Jan 7, 2013 at 12:23 AM, Edward Diener > <eldlistmailingz at tropicsoft.com> wrote: >> On Mageia 2 I have installed the binary clang package clang3.0-7. When I >> tried to build the latest llvm/clang from source using this binary clang >> I get this error: >> >> 1) In file included from >>

On Sat, Jul 30, 2011 at 2:35 AM, 陳韋任 <chenwj at iis.sinica.edu.tw> wrote: > Hi, Asron > > > This looks relevant to me for your issue. Grabbing the cxxabi.h from > there > > may work: > > > > http://comments.gmane.org/gmane.comp.compilers.clang.devel/9391 > > I am not sure where to put cxxabi.h. How can I let clang find this > header file while

If you're willing to install libc++ you can easily work around this by running `ninja install-cxx install-cxxabi` before running any of the LLVM or Clang build targets. /Eric On Tue, Dec 27, 2016 at 7:45 AM, Carsten Mattner via llvm-dev < llvm-dev at lists.llvm.org> wrote: > On Tue, Dec 27, 2016 at 3:38 PM, Asiri Rathnayake > <asiri.rathnayake at gmail.com> wrote: >

On Mon, Jan 7, 2013 at 12:23 AM, Edward Diener <eldlistmailingz at tropicsoft.com> wrote: > On Mageia 2 I have installed the binary clang package clang3.0-7. When I > tried to build the latest llvm/clang from source using this binary clang > I get this error: > > 1) In file included from > /home/mgeldiener/vcs/llvm/lib/Support/Signals.cpp:30: >

On Thu, May 5, 2016 at 10:58 AM, Duncan P. N. Exon Smith via llvm-dev < llvm-dev at lists.llvm.org> wrote: > +Kate > > We already have two demangler implementations (LLDB and libcxxabi). I'd > rather not have three. Have you looked at the LLDB one? I think Kate has > some patches she hasn't had a chance to commit yet that add functionality. > I heard something

On Mon, Jan 7, 2013 at 12:23 AM, Edward Diener <eldlistmailingz at tropicsoft.com> wrote: > On Mageia 2 I have installed the binary clang package clang3.0-7. When I > tried to build the latest llvm/clang from source using this binary clang > I get this error: > > 1) In file included from > /home/mgeldiener/vcs/llvm/lib/Support/Signals.cpp:30: >

On Mageia 2 I have installed the binary clang package clang3.0-7. When I tried to build the latest llvm/clang from source using this binary clang I get this error: 1) In file included from /home/mgeldiener/vcs/llvm/lib/Support/Signals.cpp:30: /home/mgeldiener/vcs/llvm/lib/Support/Unix/Signals.inc:32:10: fatal error: 'cxxabi.h' file not found #include <cxxabi.h> ^ llvm[1]:

> On May 5, 2016, at 11:50 AM, Duncan P. N. Exon Smith <dexonsmith at apple.com> wrote: > >> On 2016-May-05, at 11:14, David Majnemer <david.majnemer at gmail.com> wrote: >> >> On Thu, May 5, 2016 at 10:58 AM, Duncan P. N. Exon Smith via llvm-dev <llvm-dev at lists.llvm.org> wrote: >>> +Kate >>> >>> We already have two

If you want to get the original name by a library function, as Jonathan mentioned, you can call __cxa_demangle in cxxabi.h. However, this API is only available in gcc. If you want something more portable, try glog or libibert, notice libibert is GPL licensed. On Thu, Dec 11, 2014 at 7:57 AM, Roel Jordans <r.jordans at tue.nl> wrote: > When a C++ compiler translates source code it will

Hi James, We've indeed passed the appropriate (and even excessive) flags to the appropriate pipeline parts, that is: llvm-gcc -O1 -fno-omit-frame-pointers -g $in -emit-llvm -S -o $name.ll llc --disable-fp-elim $name.ll -o $name.S g++ -fno-omit-frame-pointers -c $name.S , but that didn't work Alex On Tue, Apr 5, 2011 at 4:40 PM, James Molloy <James.Molloy at arm.com> wrote:

On Tue, Dec 27, 2016 at 3:38 PM, Asiri Rathnayake <asiri.rathnayake at gmail.com> wrote: > > > On Tue, Dec 27, 2016 at 1:29 PM, Carsten Mattner via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> >> When I tried to build with -DLLVM_ENABLE_LIBCXX, I found out that >> it doesn't try to use the in-tree libcxx but looks for one built >> and

Was there any resolution about if bringing this into the LLVM Support directory should be done or not? I have a need of being able to use this, not just for demangling, but also to verify correctness of a mangled function, and can only rely on LLVM core. Thanks, Micah > -----Original Message----- > From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] > On Behalf