similar to: [LLVMdev] Weird Exception Handling Compilation Bug

On Mon, 10 Sep 2007, Bill Wendling wrote: > When I compile the following program with llvm-gcc on Mac x86, it segfaults: > However, if I compile it to a .s file and then compile it with gcc, it > works fine: > This is weird. Anyone have an idea of what's going on? They are probably linking against different libstdc++ versions. Passing -v to the compiler should print the command

On 9/10/07, Chris Lattner <sabre at nondot.org> wrote: > On Mon, 10 Sep 2007, Bill Wendling wrote: > > When I compile the following program with llvm-gcc on Mac x86, it segfaults: > > However, if I compile it to a .s file and then compile it with gcc, it > > works fine: > > This is weird. Anyone have an idea of what's going on? > > They are probably

Hi Bill, I committed a fix already as r355743 [1], and it fixes `test2` as well. I believe we should merge this into 8.0. /Eric [1] https://github.com/llvm/llvm-project/commit/680e865c313a80b6ec329abde61e1f0c66bdc103 On Fri, Mar 8, 2019 at 5:46 PM Bill Wendling <isanbard at gmail.com> wrote: > Hi Eric, > > The attached patch may help matters, though it now fails because

Hi all, I'm compiling this trivial program on Darwin: int main(int argc, char **argv) { try { throw argc; } catch(int i) { return i; } return 0; } However, it segfaults when I run it. I've attached the .s files generated by LLVM and GCC, but it looks as if LLVM isn't generating a gxx_personality_v0 section (like it does for Unwind_Resume, et al). Is this what's

On 8/24/07, Chris Lattner <sabre at nondot.org> wrote: > > so how about turning it on? > > It sounds good, but I'm concerned about darwin/x86. Bill, can you see how > well darwin/x86 is doing these days? If there are no regressions from > turning this on by default, we should do it. :) > I'm assuming that this is 4.2? :-) I'll give it a try. -bw

For those who are playing along, I've started on the exception handling rewrite following the document and comments from this thread: http://lists.cs.uiuc.edu/pipermail/llvmdev/2011-July/041748.html The repositories are: http://llvm.org/svn/llvm-project/llvm/branches/exception-handling-rewrite http://llvm.org/svn/llvm-project/cfe/branches/exception-handling-rewrite Progress Report: I

This is a revision of the second exception handling proposal I sent out. You can see it here: http://lists.cs.uiuc.edu/pipermail/llvmdev/2010-November/036484.html After much discussion, there are some changes to the proposal – some significant and some minor. One major point, this proposal does not address the issue of catching an exception thrown from a non-invoke instruction. However if done

Hi, > thank for your answer. Is there any document/tutorial about linking > bytecode file with libstdc++ avaiable ? first you need to compile the bitcode to assembler using llc. For example: llc bitcode.bc This produces bitcode.s. Turn this into a executable using: llvm-g++ -o bitcode bitcode.s or g++ -o bitcode bitcode.s It doesn't matter which g++ you use here. Using g++

On Mar 16, 2008, at 5:07 AM, Duncan Sands wrote: >> Did anything ever come of the work on exception handling for x86_64? >> >> I'm having problems with exceptions on linux x86_64. > > I'm fairly sure that exception handling doesn't currently work on > x86-64 linux (it may work with darwin - not sure). I don't know > what it would take to get it to

On Sat, 2006-11-04 at 21:06 -0800, Reid Spencer wrote: > Hi Napi, > > On Sun, 2006-11-05 at 12:40 +0800, Mohd-Hanafiah Abdullah wrote: > > Hi: > > > > I'm interested in using llvm to convert C++ code to C code. > > I used the following command to do this: > > > > % llvm-g++ -c foo.cpp -o - | llc -march=c -o foo.cbe.c > > Yup, that'll

Hi All, I know we're late in the release process, but I've discovered a regression I believe is serious enough to hold the release [1]. The regression is in usages of `__builtin_constant_p` applied to a dereferenced pointer in a constant expression. In certain cases Clang now rejects this as a non-constant expression [2]. This regression will have a larger impact than it initially

On Jul 23, 2008, at 11:31 AM, Duncan Sands wrote: >> I have tried to compile a simple cpp file with llvm-gcc. I have >> attached >> the assemble file here. >> I see a weird thing there. There are some call instructions, they >> call the >> function "@_Znwj". But this function was only declared in the file, >> there is >> no

Hi Anton & Duncan, When I try to compile on Darwin now, I get this: $ /Volumes/Gir/devel/llvm/llvm-gcc-4.0.obj/gcc/xgcc <options> -o eh_alloc.o Assertion failed: (false && "Couldn't find the register class"), function getPhysicalRegisterRegClass, file /Volumes/Gir/devel/llvm/ llvm.src/lib/CodeGen/SelectionDAG/ScheduleDAG.cpp, line 269.

Bill Wendling wrote: > On Wed, Jan 21, 2009 at 3:40 PM, Dave Nadler <Dave.Nadler at nadler.com> wrote: > >> Hi All - Newbie warning... I am developing for a target that does not have >> a functioning C++ environment, and need to use C++. It was suggested that I >> could use LLVM to compile to C (using llc -march=c), then run the resulting >> C-code through

On 9/25/07, Daniel Berlin <dberlin at dberlin.org> wrote: > On 9/24/07, Bill Wendling <isanbard at gmail.com> wrote: > > On Sep 24, 2007, at 3:15 PM, Dale Johannesen wrote: > > > > Weird. I see a potential problem, though. The code is like this: > > > > void dumpToDOUT(SparseBitVector<> *bitmap) { > > dump(*bitmap, DOUT); > > } >

Nick, Can you take a quick look at the asan_eh_bug.tar.bz testcase I uploaded into the newly opened radr://12777299, "potential pthread/eh bug exposed by libsanitizer". The FSF gcc developers have ported llvm.org's asan code into FSF gcc (and are keeping it synced to the upstream llvm.org code). I have been helping with the darwin build and testing -fsanitize=address against the

Jack, can you please upload this test somewhere? On Thu, Nov 29, 2012 at 10:09 AM, Kostya Serebryany <kcc at google.com> wrote: > +glider > The compiler hardly matters here, I would expect the same failures with > clang. > Alex, could you please take a look? > > --kcc > > > On Thu, Nov 29, 2012 at 9:55 PM, Jack Howarth <howarth at bromo.med.uc.edu> >

Hi, thank for your answer. Is there any document/tutorial about linking bytecode file with libstdc++ avaiable ? Quang -----Ursprüngliche Nachricht----- Von: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] Im Auftrag von Chris Lattner Gesendet: Mittwoch, 23. Juli 2008 20:35 An: LLVM Developers Mailing List Cc: Le Anh Quang Betreff: Re: [LLVMdev] weird function On Jul 23,

On Dec 1, 2010, at 1:12 AM, Renato Golin wrote: > On 1 December 2010 07:04, Bill Wendling <wendling at apple.com> wrote: >> The unwind edge from an invoke instruction jumps to a landing pad. That landing pad contains code which performs optional cleanups, and then determines which catch handler to call (if any). If no catch handlers are applicable, the exception resumes propagation

On 1 December 2010 07:04, Bill Wendling <wendling at apple.com> wrote: > The unwind edge from an invoke instruction jumps to a landing pad. That landing pad contains code which performs optional cleanups, and then determines which catch handler to call (if any). If no catch handlers are applicable, the exception resumes propagation either to the next enclosing region or out of the