search for: eh

...er my understanding is that they aren't.   >> On the basis that they're intended for use by llvm geeks, I think   >> either of these is an improvement, except in the second case I think   >> the default should be target-dependent.  Comments? > How about having -enable-eh turn on dwarf eh on all targets (including > those that don't support it, in which case intrinsics get lowered to > nothing much IIRC), and also have it cause a LowerInvoke pass to be run > on targets that do not support dwarf eh. This also makes sense to me. The disadvantage being t...

Hi Dale, > Chris would like to turn on -enable-eh rather than -enable-correct-eh- > support in the llvm testsuite for those targets that support it.  The   > following patch is intended to turn it on for x86 and ppc.  Anton,   > Duncan, are you OK with this? yes, though see below. > Chris would also like to discuss renaming the EH c...

Chris would like to turn on -enable-eh rather than -enable-correct-eh- support in the llvm testsuite for those targets that support it. The following patch is intended to turn it on for x86 and ppc. Anton, Duncan, are you OK with this? -------------- next part -------------- A non-text attachment was scrubbed... Name: mf.patch T...

Hi Duncan, I hacked together a version of DwarfEHPrepare.cpp which tries to deal with the ordering of llvm.eh.exception and llvm.eh.selector. The hacked is contained within the attached patch. Motivation: I recently created a decent amount of hand coded IR (via the llvm C++ API). In order to help me runtime debug the code, I created automatic c...

...res in MCJIT. It this something known or expected? I build LLVM/clang with pre-packaged clang-3.7.0, with "-stdlib=libc++". Example failure: /w/bld/org/./bin/lli -remote-mcjit -mcjit-remote-process=/w/bld/org/./bin/lli-child-target /w/src/llvm.org/test/ExecutionEngine/MCJIT/remote/eh.ll -- Exit Code: 184 Command Output (stderr): -- warning: remote mcjit does not support lazy compilation terminating with uncaught exception of type int ERROR: Unexpected RPC call -- ******************** FAIL: LLVM :: ExecutionEngine/MCJIT/eh.ll (18164 of 33466) ******************** TEST 'LL...

Hi, >> from the exist llvm-ir it seems there are some common info for sjlj-eh >> and dwarf-eh! >> are there possible use the exist llvm-ir to generate exception table > >for sjlj-eh ? >No. There should be support from llvm-gcc. sjlj eh and dwarf eh have >different semantics different semantics ? ! I think llvm-gcc generate the IR should not includ...

Hi Garrison, > I hacked together a version of DwarfEHPrepare.cpp which tries to deal with the ordering of llvm.eh.exception and llvm.eh.selector. > The hacked is contained within the attached patch. it looks like you tried to copy the code for eh.exception. There are two problems with this: (1) the eh.exception code really needs to be rewritten t...

...>>> aren't. On the basis that they're intended for use by llvm >>> geeks, I think >>> either of these is an improvement, except in the second case I think >>> the default should be target-dependent. Comments? > >> How about having -enable-eh turn on dwarf eh on all targets >> (including >> those that don't support it, in which case intrinsics get lowered to >> nothing much IIRC), and also have it cause a LowerInvoke pass to be >> run >> on targets that do not support dwarf eh. > > This also m...

...gleSource/UnitTests/Vector/sumarray llc /SingleSource/UnitTests/Vector/sumarray-dbl jit /SingleSource/UnitTests/Vector/sumarray-dbl cbe /SingleSource/UnitTests/Vector/sumarray-dbl ^^ all of the above fail because my 3.4.6 compiler doesn't support vectors well llc /SingleSource/Regression/C++/EH/ctor_dtor_count-2 jit /SingleSource/Regression/C++/EH/ctor_dtor_count-2 cbe /SingleSource/Regression/C++/EH/ctor_dtor_count-2 llc /SingleSource/Regression/C++/EH/ctor_dtor_count jit /SingleSource/Regression/C++/EH/ctor_dtor_count cbe /SingleSource/Regression/C++/EH/ctor_dtor_count llc /SingleSource...

...build > LLVM/clang with pre-packaged clang-3.7.0, with "-stdlib=libc++". > > > Example failure: > > /w/bld/org/./bin/lli -remote-mcjit > -mcjit-remote-process=/w/bld/org/./bin/lli-child-target > /w/src/llvm.org/test/ExecutionEngine/MCJIT/remote/eh.ll > <http://llvm.org/test/ExecutionEngine/MCJIT/remote/eh.ll> > -- > Exit Code: 184 > > Command Output (stderr): > -- > warning: remote mcjit does not support lazy compilation > terminating with uncaught exception of type int > ERROR...

...handle_float(); } keep_going(); } ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ; Original ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ; Function Attrs: uwtable define void @_Z4testv() #0 { entry: %outer = alloca %class.Outer, align 1 %inner = alloca %class.Inner, align 1 call void @llvm.eh.setehstate(i32 0) invoke void @_ZN5OuterC1Ev(%class.Outer* %outer) to label %invoke.cont unwind label %lpad invoke.cont: call void @llvm.eh.setehstate(i32 1) call void @llvm.eh.setehstate(i32 2) invoke void @_ZN5InnerC1Ev(%class.Inner* %inner) to label %invoke.cont1 unw...

...to Bill's. It is closer to what we already have (which can be seen as a good or a bad thing!), and is also closer to what gcc does. It is more incremental than Bill's and introduces fewer new concepts. Executive summary ----------------- Remove the personality and list of catches out of eh.selector and stick them directly on invoke instructions. The invoke instruction ---------------------- The invoke instruction is modified by adding extra catch info to it: <result> = invoke <function>(<function args>) to label <normal label> unwind label <excep...

I accidentally ran into a JIT scenario where a call instruction, executing an external non-generated C function, executed between a llvm.eh.exception and a llvm.eh.selector instruction would clobber the register (register index __builtin_eh_return_data_regno(1)), used by the return value of llvm.eh.selector. The behavior of the call depends on the function called even though none of the functions I have tested played with the excepti...

...n smb.conf, in station log is suspicious record about closing file with filedescriptor fd=-1 : [2002/06/07 14:33:53, 4] smbd/open.c:open_file_shared1(891) calling open_file with flags=0x0 flags2=0x0 mode=0764 [2002/06/07 14:33:53, 2] smbd/open.c:open_file(230) johny opened file O/a1/KO-I_X8-eh.dft read=Yes write=No (numopen=1) reply_ntcreate_and_X: fnum = 5004, open name = O/a1/KO-I_X8-eh.dft switch message SMBclose (pid 6617) pipe name srvsvc pnum=71e8 (pipes_open=1) [2002/06/07 14:33:53, 5] smbd/pipes.c:reply_pipe_close(255) reply_pipe_close: pnum:71e8 [2002/06/07 14:33:53,...

...le.com > Nickname: OldGrawp-O0-PIC > Buildstatus: OK > > New Test Passes: > test/CFrontend/2008-01-28-PragmaMark.c [DEJAGNU] > > > New Test Failures: > Benchmarks/Shootout-C++/except [LLC compile, ] > Benchmarks/tramp3d-v4/tramp3d-v4 [LLC compile, ] > Regression/C++/EH/ctor_dtor_count [LLC compile, ] > Regression/C++/EH/ctor_dtor_count-2 [LLC compile, ] > Regression/C++/EH/exception_spec_test [LLC compile, ] > Regression/C++/EH/function_try_block [LLC compile, ] > Regression/C++/EH/simple_rethrow [LLC compile, ] > Regression/C++/EH/simple_throw [LL...

Folks, I'm sorry for getting at this again, but this will not be the last discussion on the topic, so let's just get to business. We're about to merge the last critical patch to make EHABI compatible with other EH mechanisms in LLVM (D3079), and that has unearthed a few issues with the function attributes. Logan's blog post [1] contains a proposal to split unwinding from exceptional logic which I think we should give it a try. I'm trying to make it as backward compatible...

Hi Garrison, > I accidentally ran into a JIT scenario where a call instruction, executing an external non-generated C function, > executed between a llvm.eh.exception and a llvm.eh.selector instruction would clobber the register > (register index __builtin_eh_return_data_regno(1)), used by the return value of llvm.eh.selector. The behavior > of the call depends on the function called even though none of the functions I have tested played with t...

On Dec 1, 2010, at 1:37 PM, Duncan Sands wrote: > Executive summary > ----------------- > > Remove the personality and list of catches out of eh.selector and stick them > directly on invoke instructions. > > The invoke instruction > ---------------------- > > The invoke instruction is modified by adding extra catch info to it: > > <result> = invoke <function>(<function args>) > to label...

On Aug 28, 2007, at 11:20 PM, Duncan Sands wrote: > Hi Bill, > >> This is a (very) rough patch to fix building LLVM with exceptions on >> PPC Darwin. Basically, it puts the burden of adding the "--enable-eh" >> on the specific target, which is where I think it should go. > > I don't like it. LLVM has plenty of features that are not supported > on all targets, why should it be the responsability of llvm-gcc to > manage > this particular one and not the others? It is tr...

On Sat, 18 Nov 2006, [ISO-8859-2] Žiga Osolin wrote: > I am currently trying to make EH (exception handling) possible to be > integrated in C++. This means that C++ code can throw exceptions and > llvm code can catch such exception and llvm can throw exceptions that > C++ can catch (or pass through). There are quite some difficulties with > approach: Cool! This is the ma...