similar to: [LLVMdev] invoke unwind instruction support in 2.9

On Aug 13, 2011, at 4:44 PM, Carter Cheng wrote: > Hello, > > I was looking over the documentation support for exceptions and it indicates that the invoke unwind support is incomplete. Is this still the case in 2.9? > Hi Carter, The use of the term "unwind" is a bit confusing in this context. The "invoke" instruction has an "unwind" clause, which is

Thanks Hal. On Fri, Oct 28, 2011 at 2:19 AM, Hal Finkel <hfinkel at anl.gov> wrote: > Carter, > > In my opinion (and I was the one who committed the changes in question), > it depends on the hardware. The pipeline descriptions are for the PPC > 440, which is an embedded PPC chip use in a variety of places. As such, > it is a fairly specific target, and using

I hope you don't mind if do have a follow up question- is code in place in the code generation supporting "proper" scheduling via the processor itineraries in LLVM? On Fri, Oct 28, 2011 at 8:47 PM, Carter Cheng <cartercheng at gmail.com> wrote: > Thanks Hal. > > On Fri, Oct 28, 2011 at 2:19 AM, Hal Finkel <hfinkel at anl.gov> wrote: > >> Carter,

Thanks for the help. I have a couple follow up questions- Where can I find the code which calculates the properties of inline asm nodes and examples of passes that make use of this information? Thanks again, Carter. On Mon, Nov 5, 2018 at 12:04 AM David Blaikie <dblaikie at gmail.com> wrote: > > > On Sun, Nov 4, 2018 at 1:56 AM Carter Cheng via llvm-dev < > llvm-dev at

On Mon, Jun 15, 2009 at 9:40 PM, Duncan Sands<baldrick at free.fr> wrote: > you can call the libgcc/libunwind routines directly.  There was an > example of this on the mailing list by Talin not long ago. I'll look into this. Thanks. > That said, > it wouldn't be too hard to support "unwind" in the code generators. > It would basically mean creating

Hi Wesley, > The documentation of unwind/invoke is quite clear and does exactly > what I need: unwinding the stack. I don't need it to carry an object > back. I don't need it to figure out what the type of the object is or > what catch() blocks it matches. I just need it to unwind the stack. > The rest is my job as a part of the runtime. Unfortunately, I have > learned

Here is a small doc patch based on answers from the list and from the links mentioned. For stylistic consistency I've followed the language in the va_arg description for the analogous situation. Dustin -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: LangRef.unwind.patch URL:

The documentation of unwind/invoke is quite clear and does exactly what I need: unwinding the stack. I don't need it to carry an object back. I don't need it to figure out what the type of the object is or what catch() blocks it matches. I just need it to unwind the stack. The rest is my job as a part of the runtime. Unfortunately, I have learned that while this works with the bytecode

Hi Dustin, > Here is a small doc patch based on answers from the list and from the > links mentioned. For stylistic consistency I've followed the language > in the va_arg description for the analogous situation. as I mentioned in another email, unwind is not completely unsupported: it does work for rethrowing an exception. Ciao, Duncan.

On Mon, Jun 15, 2009 at 7:08 PM, Aaron Gray<aaronngray.lists at googlemail.com> wrote: >> The documentation of unwind/invoke is quite clear and does exactly >> what I need: unwinding the stack. I don't need it to carry an object >> back. I don't need it to figure out what the type of the object is or >> what catch() blocks it matches. I just need it to unwind

> The documentation of unwind/invoke is quite clear and does exactly > what I need: unwinding the stack. I don't need it to carry an object > back. I don't need it to figure out what the type of the object is or > what catch() blocks it matches. I just need it to unwind the stack. > The rest is my job as a part of the runtime. Unfortunately, I have > learned that while

Hi Dustin, the code generators do not support unwind, only the interpreter does. Ciao, Duncan.

I put invoke/unwind aside because I couldn't get them to work, but I'm working on my evaluator now and it would be nice to figure this out so I don't have to unwind the stack manually. This was the reason for my earlier question about global declarations, and as that's cleared up I can easily pass exception data...if I can make unwind return out of some deep recursion. The

If an unwind instruction is called, is the does it define a return value for the corresponding invoke instruction? In other words, when we get to the exception label, will the value returned by the invoke instruction be defined? If so, how is it defined? Regards, Ryan

* Wesley W. Terpstra: > The documentation of unwind/invoke is quite clear and does exactly > what I need: unwinding the stack. I don't need it to carry an object > back. I don't need it to figure out what the type of the object is or > what catch() blocks it matches. I just need it to unwind the stack. You can use your stack switching mechanism for this purpose.

Florian Weimer wrote: > * Wesley W. Terpstra: > >> The documentation of unwind/invoke is quite clear and does exactly >> what I need: unwinding the stack. I don't need it to carry an object >> back. I don't need it to figure out what the type of the object is or >> what catch() blocks it matches. I just need it to unwind the stack. > > You can use your

On Wed, Jan 13, 2010 at 4:07 AM, Duncan Sands <baldrick at free.fr> wrote: > Hi Dustin, the code generators do not support unwind, only the > interpreter does. > > Ciao, > > Duncan. > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu >

If it helps, to see what is involved, outside of a pure IR context, see the example code, and doc at: http://wiki.llvm.org/HowTo:_Build_JIT_based_Exception_mechanism#Source_Code:_exceptionDemo.cpp Although this is a pure example that shows several test cases, including foreign exception interaction, it is not an IR example, but rather a LLVM IR API example. It would be interesting to see a pure

On 01/13/2010 01:52 PM, Duncan Sands wrote: > as I mentioned in another email, unwind is not completely unsupported: > it does work for rethrowing an exception. Good point. Not understanding how languages implement exceptions under the hood, I lose the nuances that should be in a reference document. How's this version? Dustin -------------- next part -------------- An embedded and

On 01/13/2010 02:07 AM, Duncan Sands wrote: > Hi Dustin, the code generators do not support unwind, only the > interpreter does. Ah, the secret is not to even try to frob the gnorts. Manual unwinding, here I come. :-( I was going to say the interpreter doesn't either, but then I recalled it JITs when it can. I don't know how to call into libc from the interpreter to test that.