similar to: [LLVMdev] Fw: RTTI gone in 3.0?

Den 18.07.2011 17:40, skrev Samuel Crow: > Hi FlyLanguage, > > I thought LLVM disabled RTTI a long time ago. It was just too slow. > > --Sam No, it was used a few places until fairly recently at least, and I'm not sure if it's totally gone yet. The custom rtti stuff didn't catch quite all the cases I think. Anyone?

Just wondering if rtti will be gone in 3.0? I'd like to port llvm to my OS, where the gcc runtime env has rtti turned off. Thanks.

----- Original Message ---- > From: Óscar Fuentes <ofv at wanadoo.es> > To: Samuel Crow <samuraileumas at yahoo.com> > Cc: Óscar Fuentes <ofv at wanadoo.es>; LLVM Developers Mailing List ><llvmdev at cs.uiuc.edu> > Sent: Fri, January 14, 2011 4:39:57 PM > Subject: Re: Circular Deps from CMake build using makefile > > Samuel Crow <samuraileumas

Whoops, phone rang and I forgot to cc to the list before I typed the message. ----- Forwarded Message ---- > From: Samuel Crow <samuraileumas at yahoo.com> > To: Ruben Van Boxem <vanboxem.ruben at gmail.com> > Sent: Wed, January 5, 2011 3:38:21 PM > Subject: Re: [LLVMdev] include/Config/config.h discrepancies between CMake and >autofoo builds > > > >

Hello Óscar, This time the autotools version of LLVM trunk build with Clang trunk compiled in Debug+Asserts mode without complaint with --enable-bindings=none. I suspect this makes something fishy looking with the CMake build. Do you need logfiles from configure? Thanks again, --Sam ----- Original Message ---- > From: Óscar Fuentes <ofv at wanadoo.es> > To: Samuel Crow

Hello Óscar, The single-threaded build failed the same place as the double threaded build failed which is the same place I just indicated in my previous post. The ../llvm/configure script version failed with OCaml building with about 600 assembler errors since I built it in AMD64 mode. (Oops.) Should I disable OCaml from the configure script and try again? Assembler error, input left in

In that case, RTTI and exception should also be disabled from CMake generated projects right? Currently they are enabled all over my MSVC projects. On Thu, Oct 14, 2010 at 3:57 AM, Duncan Sands <baldrick at free.fr> wrote: > Hi Al, > >> It's good that llvm/lib builds with exceptions and RTTI disabled as it >> supports doing optimization and codegen on very constrained

Samuel Crow <samuraileumas at yahoo.com> writes: > This time the autotools version of LLVM trunk build with Clang trunk compiled in > Debug+Asserts mode without complaint with --enable-bindings=none. I suspect > this makes something fishy looking with the CMake build. Do you need logfiles > from configure? I'm clueless about what's happening there. The cyclic

Samuel Crow <samuraileumas at yahoo.com> writes: > I have attached the logfiles here. I think you didn't set CMAKE_BUILD_TYPE while configuring the cmake build. On your build directory, please do: make clean cmake -DCMAKE_BUILD_TYPE=Debug path/to/your/llvm/source/root make If that doesn't work, show the exact command lines you used for invoking cmake and the

Hi, It's good that llvm/lib builds with exceptions and RTTI disabled as it supports doing optimization and codegen on very constrained platforms. Judging by REQUIRES_EH in makefiles, only a few bits like TableGen, llvm-ar and llvm-ranlib need them, and I doubt these would need to run on a target. It's unlikely exceptions would get in in a random patch, because it would have to change the

Hi, I've developed editor prototype for TableGen files (td). It is Eclipse plugin based on IMP project (The IDE Meta-Tooling Platform). Editor has outline, folding, coloring, go to definition, etc. As any prototype, editor has some limitations (e.g. no cross-file indexing). If there is any interest to such tool I will improve it a bit and then publish. Also considering llvm asm (ll) editing

Sorry, forgot to CC the list. ----- Forwarded Message ----- > From: Samuel Crow <samuraileumas at yahoo.com> > To: Joachim Durchholz <jo at durchholz.org> > Cc: > Sent: Tuesday, May 31, 2011 9:35 PM > Subject: Re: [LLVMdev] Thinking about "whacky" backends > > Hello, > > > ----- Original Message ----- >> From: Joachim Durchholz

Hi Chris, I was thinking that CreateValueName() was the way to add a symbol to a symbol table. Perhaps I'm thinking about this wrong. Here's what I've got: I've got a string generated by the parser which is constant. I need to add it to the symbol table so that, on starting the second pass of my compiler, I can dump all of the string constants to be generated as code. I

I build llvm+clang almost every day with Ubuntu 10.04. Everything goes fine. I guess it's your VirtualBox has too little memory. On Thu, May 6, 2010 at 4:12 AM, Samuel Crow <samuraileumas at yahoo.com> wrote: > After waiting through about 2 hours of hard drive spinning for Clang to > link under my Xubuntu Lucid Lynx Linux setup on VirtualBox, ld finally just > gave up trying

Samuel Crow <samuraileumas at yahoo.com> writes: > The single-threaded build failed the same place as the double threaded build > failed which is the same place I just indicated in my previous post. The > ../llvm/configure script version failed with OCaml building with about 600 > assembler errors since I built it in AMD64 mode. (Oops.) Should I disable > OCaml from

Samuel Crow <samuraileumas at yahoo.com> writes: > Here's some of what it would take to make portable bitcodes in C or LLVM Assembly: A look at the work done on ANDF in the 90's may be helpful. I've only skimmed it but there's been some deep thinking about stuff like this. -Dave

Forgot to CC the list. ----- Forwarded Message ---- > From: Samuel Crow <samuraileumas at yahoo.com> > To: Trevor Elliott <trevor at galois.com> > Sent: Fri, January 14, 2011 7:33:15 PM > Subject: Re: [LLVMdev] LLVM GC > > Hi Trevor, > > Are you linking with LibStdC++ or LibC++? That is a requirement for running > code that has been compiled from C++

Hi Al, > It's good that llvm/lib builds with exceptions and RTTI disabled as it > supports doing optimization and codegen on very constrained platforms. > Judging by REQUIRES_EH in makefiles, only a few bits like TableGen, llvm-ar > and llvm-ranlib need them, and I doubt these would need to run on a target. > It's unlikely exceptions would get in in a random patch, because

Hi Sam, I've not actually gotten to the linking process with my runtime, as I've compiled it with clang -emit-llvm -c, and then archived it with llvm-ar and llvm-ranlib. I'm also not producing a GC plugin, as I'm using the builtin "shadow-stack" strategy. My current build process looks like this: 1. build the compiler 2. build the runtime using clang -emit-llvm -c

Samuel Crow <samuraileumas at yahoo.com> writes: > [ 73%] Regenerating > /Users/samuraicrow/Documents/workspace/llvm-trunk-build/tools/llvm-config/LibDeps.txt.tmp > > [ 73%] Updating > /Users/samuraicrow/Documents/workspace/llvm-trunk-build/tools/llvm-config/LibDeps.txt > if necessary... > [ 73%] Checking for cyclic dependencies between LLVM libraries. >