search for: longjumps

On 8/22/20 8:26 PM, Tomas Kalibera wrote: > On 8/22/20 7:58 PM, Jeroen Ooms wrote: >> On Sat, Aug 22, 2020 at 8:39 AM Tomas Kalibera >> <tomas.kalibera at gmail.com> wrote: >>> On 8/21/20 11:45 PM, m19tdn+9alxwj7d2bmk--- via R-devel wrote: >>>> Ah yes, this is related. I reported v2010 below, but it looks like >>>> I was updated to this

On Wed, 2019-02-06 at 16:00 +0100, Joakim Tjernlund wrote: > On Tue, 2019-02-05 at 14:07 -0800, H. Peter Anvin via Syslinux wrote: > > CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. > > > > > > Hi all, > > > > It has been the case for

On 8/22/20 9:33 PM, Jeroen Ooms wrote: > On Sat, Aug 22, 2020 at 9:10 PM Tomas Kalibera <tomas.kalibera at gmail.com> wrote: >> On 8/22/20 8:26 PM, Tomas Kalibera wrote: >>> On 8/22/20 7:58 PM, Jeroen Ooms wrote: >>>> On Sat, Aug 22, 2020 at 8:39 AM Tomas Kalibera >>>> <tomas.kalibera at gmail.com> wrote: >>>>> On 8/21/20 11:45

On Wed, Aug 26, 2020 at 7:54 PM Tomas Kalibera <tomas.kalibera at gmail.com> wrote: > > On 8/25/20 6:14 PM, Tomas Kalibera wrote: > > On 8/22/20 9:33 PM, Jeroen Ooms wrote: > >> On Sat, Aug 22, 2020 at 9:10 PM Tomas Kalibera > >> <tomas.kalibera at gmail.com> wrote: > >>> On 8/22/20 8:26 PM, Tomas Kalibera wrote: > >>>> On

On Sat, Aug 22, 2020 at 8:39 AM Tomas Kalibera <tomas.kalibera at gmail.com> wrote: > > On 8/21/20 11:45 PM, m19tdn+9alxwj7d2bmk--- via R-devel wrote: > > Ah yes, this is related. I reported v2010 below, but it looks like I was updated to this Insider Build overnight without my knowledge, and conflated it with the new installation R v4 this morning. > > > > I will

On Sun, Dec 18, 2016 at 02:23:01PM +0100, Jonas Maebe via llvm-dev wrote: > Recap: we use setjmp/longjmp for our exception handling on all platforms in > our regular (non-LLVM) code generators. I'd like to use the same > infrastructure with the LLVM code generator for code interoperability > purposes (the LLVM SjLj personality is not binary-compatible with our > existing

On 8/22/20 7:58 PM, Jeroen Ooms wrote: > On Sat, Aug 22, 2020 at 8:39 AM Tomas Kalibera <tomas.kalibera at gmail.com> wrote: >> On 8/21/20 11:45 PM, m19tdn+9alxwj7d2bmk--- via R-devel wrote: >>> Ah yes, this is related. I reported v2010 below, but it looks like I was updated to this Insider Build overnight without my knowledge, and conflated it with the new installation R

On Sat, Aug 22, 2020 at 9:10 PM Tomas Kalibera <tomas.kalibera at gmail.com> wrote: > > On 8/22/20 8:26 PM, Tomas Kalibera wrote: > > On 8/22/20 7:58 PM, Jeroen Ooms wrote: > >> On Sat, Aug 22, 2020 at 8:39 AM Tomas Kalibera > >> <tomas.kalibera at gmail.com> wrote: > >>> On 8/21/20 11:45 PM, m19tdn+9alxwj7d2bmk--- via R-devel wrote: >

On 30/09/16 20:10, Reid Kleckner wrote: > On Mon, Sep 19, 2016 at 4:42 AM, Jonas Maebe <jonas-devlists at watlock.be > <mailto:jonas-devlists at watlock.be>> wrote: > > So, can I use invoke and landingpad without using any of the other > exception handling intrinsics? (in combination with a dummy personality > function) Or will LLVM in all cases insist on

On Wed, Feb 6, 2019 at 2:35 PM H. Peter Anvin via Syslinux <syslinux at zytor.com> wrote: > > On 2/6/19 9:17 AM, Joakim Tjernlund via Syslinux wrote: > > On Wed, 2019-02-06 at 16:00 +0100, Joakim Tjernlund wrote: > >> On Tue, 2019-02-05 at 14:07 -0800, H. Peter Anvin via Syslinux wrote: > >>> CAUTION: This email originated from outside of the organization. Do

On 8/25/20 6:14 PM, Tomas Kalibera wrote: > On 8/22/20 9:33 PM, Jeroen Ooms wrote: >> On Sat, Aug 22, 2020 at 9:10 PM Tomas Kalibera >> <tomas.kalibera at gmail.com> wrote: >>> On 8/22/20 8:26 PM, Tomas Kalibera wrote: >>>> On 8/22/20 7:58 PM, Jeroen Ooms wrote: >>>>> On Sat, Aug 22, 2020 at 8:39 AM Tomas Kalibera >>>>>

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

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

On 01/13/2010 04:08 AM, Garrison Venn wrote: > 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 It does, although in the "let me show you why this is too much to tackle" way. > Although this is a pure example that

On 2/6/19 9:17 AM, Joakim Tjernlund via Syslinux wrote: > On Wed, 2019-02-06 at 16:00 +0100, Joakim Tjernlund wrote: >> On Tue, 2019-02-05 at 14:07 -0800, H. Peter Anvin via Syslinux wrote: >>> CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. >>>

On Thu, 2019-02-07 at 06:12 -0500, Gene Cumm wrote: > On Wed, Feb 6, 2019 at 2:35 PM H. Peter Anvin via Syslinux > <syslinux at zytor.com> wrote: > > On 2/6/19 9:17 AM, Joakim Tjernlund via Syslinux wrote: > > > On Wed, 2019-02-06 at 16:00 +0100, Joakim Tjernlund wrote: > > > > On Tue, 2019-02-05 at 14:07 -0800, H. Peter Anvin via Syslinux wrote: > >

...ned by the program is 0xC0000028, which is STATUS_BAD_STACK with the description: "An invalid or unaligned stack was encountered during an unwind operation". I'm not really good at C++ or makefile/compiler stuff, but I can't get it to work. I'm guessing this as to do with some longjumps to return to the prompt when there is an error but I don't know how to fix it. Compiling in 32 bits: P:/Rtools/mingw_32/bin/g++ -O3 -Wall -pedantic -IP:/R/R-3.4.3/include -c testr.cpp -o testr.o P:/Rtools/mingw_32/bin/g++ -o ./32.exe ./testr.o -LP:/R/R-3.4.3/bin/i386 -lR -lRgraphapp Results i...

Could someone refer me to documentation, or give me a brief explanation as to why the following will not work--with the caveat that I am still new to this, and have not gotten beyond generating and running jitted code via the LLVM libraries: Imagine three functions fa, fb, fc where fa, and fc are generated and jitted with llvm. Function fb on the other hand has external C linkage and is

Martin wrote: > Just this morning, > I found (again!, we had something close to this before) > the following related bugous behavior : > After interrupting a plot (which would have taken a few minutes and was > "wrong" anyway), starting another plot, interrupting again [with C-c], > and maybe the same once more, > R started just giving a ">" prompt

On 22-Aug-2001, Luke Tierney <luke@nokomis.stat.umn.edu> wrote: | We will I think have to come up with a cleaner model for very | selectively enabling interrupt processing, perhaps with some | integration with the external function registration mechanism Duncan | added recently (e.g. marking a function as one where LONGJMP's are | safe). FWIW, Octave doesn't do this correctly