similar to: [LLVMdev] Where is 'exception_cleanup' called?

Hello Hal, I have a strong suspicion that your constant folding optimization introduced at r174746 is broken on ARM. There is a bug about it: http://llvm.org/bugs/show_bug.cgi?id=15581 There is no such issue with 3.2, and reverting r174746 on top of r178740 also fixes the problem. I'm trying to fix it myself, but still have no good ideas; so it would be great to have an advice from you.

----- Original Message ----- > From: "Dmitry Antipov" <antipov at dev.rtsoft.ru> > To: "Hal Finkel" <hfinkel at anl.gov> > Cc: "Renato Golin" <renato.golin at linaro.org>, llvmdev at cs.uiuc.edu > Sent: Thursday, April 4, 2013 3:22:05 AM > Subject: Is r174746 broken on ARM? > > Hello Hal, > > I have a strong suspicion

Hello all, can someone do a quick review of the one-line proposal fix attached to http://llvm.org/bugs/show_bug.cgi?id=15581? I'm not sure that I can explain why it works, but it (hopefully) is, so I really need a feedback with this. Thanks, Dmitry

On 04/04/2013 05:09 PM, Hal Finkel wrote: > Looking briefly at the code in comment 5 of PR15581, is that the pre-decrement case? > I can't test that case on PPC, so I can certainly believe that there is a problem somewhere. > The relevant code is a little farther down: > > APInt OV = > cast<ConstantSDNode>(Offset)->getAPIntValue(); > if (AM ==

Ok, see llvm/examples/ExceptionDemo/ExceptionDemo.cpp For OS X and Linux, build llvm with the environmental variable BUILD_EXAMPLES set to 1(csh: setenv BUILD_EXAMPLES 1). If llvm is already built, it will only build the examples from clang and llvm, ExceptionDemo being one of those. If I understand your case, running ExceptionDemo with an arg of -1 emulates your scenario. Note that the

Hi Garrison, Does r101453 fix this? -Chris On Mar 22, 2010, at 12:35 PM, Garrison Venn wrote: > Ok, I've isolated the recent additions that cause the issue and supplied a patch which is NOT meant > to be applied, but instead solely exists for identification purposes for those who know what they are doing. :-) > The patch is offset from HEAD. > > The patch is a hack which

Forgot to add platform with issue: OS X 10.6.2. I have not tested elsewhere. Garrison On Mar 18, 2010, at 14:20, Garrison Venn wrote: > Hi Chris, > > The MCSymbol r98459 patch of llvm seems to have broken the ExceptionDemo example. As the example is dying in the > associated personality's first unwind search phase, which happens to have no language specific context, and is

Ok, I've isolated the recent additions that cause the issue and supplied a patch which is NOT meant to be applied, but instead solely exists for identification purposes for those who know what they are doing. :-) The patch is offset from HEAD. The patch is a hack which removes use of the MCSymbol::isDefined(...) method, as its use happens to break in the exception JIT context; both in

Hi, in ExceptionDemo code ( https://llvm.org/viewvc/llvm-project/llvm/trunk/examples/ExceptionDemo/ExceptionDemo.cpp?view=markup&sortby=file ) the function "ourPersonality" is defined. a llvm::Function is created with the same name inside function "createStandardUtilityFunctions". The llvm::Function is retrieved in function "createCatchWrappedInvokeFunction".

Hi Chris, The MCSymbol r98459 patch of llvm seems to have broken the ExceptionDemo example. As the example is dying in the associated personality's first unwind search phase, which happens to have no language specific context, and is returning a _URC_CONTINUE_UNWIND, I believe the issue is generic and not specific to the example. However I'm not sure why then this wasn't seen in one

In lib/gcc_personality_v0.c, I believe the type of the exception_cleanup member of the struct _Unwind_Exception is incorrect. It has a return type of _Unwind_Reason_Code versus a return type of void as specified in http://refspecs.freestandards.org/abi-eh-1.21.html, and as can be seen in unwind.h on Linux, and OS X 10.6.x (the latter's unwind.h is under the Developer directory tree). The

---------- Forwarded message ---------- From: charles quarra <charllsnotieneningunputocorreo at gmail.com> Date: 2012/12/13 Subject: error while linking modules with exception handling demo code To: llvmdev at cs.uiuc.edu Hi, I am building a module X with an arithmetic function foo, a module Y with an arithmetic function foo2 that invokes foo. For the invocation be a proper one (being

Attached is a patch for the non ExceptionDemo demos which gets rid of the old const qualifier usage for Type. Although I recently commited the ExceptionDemo changes, I did not want to touch code that I did not "own" without other's approval. Even though trivial, I did not test this patch. Garrison -------------- next part -------------- A non-text attachment was scrubbed... Name:

Attached is a patch which will add an exception handling example to the examples directory. This patch is a version of what I added to the wiki which in addition meets the LLVM build and coding standards requirements. The patch was tested for a debug build on CentOS LINUX, and both a debug and release build on OS X 10.6.2. Because of an #include <unwind.h>, I do not know if the patch

On Mar 23, 2012, at 4:46 PM, Bill Wendling wrote: > You need to look at how the equivalent code in C++ looks in LLVM IR. The "do something with x & y" part will be an 'invoke' that lands on at landing pad, where you will then call the d'tor to your allocated object. OK, after a lot of tinkering (and looking at the ExceptionDemo.cpp file), I have something that works

I'm proud to announce Leaf <http://leaflang.org/>, a soon to be great new programming language. I've been working over a year on it now, though it's nowhere near completion. Consider this a pre-alpha prototype stage announcement. ;) A lot of my progress is due entirely to LLVM. So while Leaf has a host of features <http://leaflang.org/features/index.html>, I'd like to

I'm seeing the following result on code which has run successfully before on Linux, and currently successfully runs on OS X 10.6.x: Stack dump: 0. Running pass 'X86 DAG->DAG Instruction Selection' on function '@outerCatchFunct' Segmentation fault This process was built as part of the LLVM tree with: setenv CC /usr/local/bin/gcc setenv CFLAGS -march=i686 setenv CXX

On Apr 8, 2012, at 10:40 PM, Bill Wendling wrote: > What gets returned by the landingpad instruction (%0 here) is normally a structure. LLVM doesn't typically treat aggregates as first-class citizens. In particular, you shouldn't store the whole structure to memory like you do to %5. You can use 'extractvalue' to get the different elements of the structure. If you need to

Hello Albert, > Any help is much appreciated. I believe examples/ExceptionDemo contains sample code which sets TargetOptions flags. In particular, llvm::EngineBuilder class has setTargetOptions() method which does all necessary magic here. -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University

On Apr 8, 2012, at 8:47 AM, Paul J. Lucas wrote: > On Apr 8, 2012, at 4:20 AM, Bill Wendling wrote: > >> On Apr 4, 2012, at 9:32 PM, Paul J. Lucas wrote: >> >>> This all seems to work just fine. I can throw a C++ exception either in a C++ object's constructor or in an ordinary member function and the stack unwinds correctly (the object's destructors are