Displaying 20 results from an estimated 1000 matches similar to: "[LLVMdev] Throwing C++ exception through LLVM JITed code"
2011 Jul 21
2
[LLVMdev] Catching exceptions passed through a JIT ExecutionEngine
Yes, I did -- it made no difference. Should it?
Note that I have since discovered that this is not a problem on Windows -- the exception drops through as expected.
pz
On 2011-07-21, at 5:45 PM, Garrison Venn wrote:
> Sorry Peter, just saw this.
>
> If you are still having the problem:
>
> Did you set: llvm::JITExceptionHandling = true; ?
>
> Garrison
>
> On Jul
2011 Jul 21
0
[LLVMdev] Catching exceptions passed through a JIT ExecutionEngine
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
2012 Dec 27
1
[LLVMdev] Throwing an exception from JITed code, and catching in C++
Hi everyone,
I am writing an application that uses LLVM JIT and I would like to throw an exception from the JIT and catch it in the C++ code that invokes the JIT.
This does not seem to work.
I've written what is hopefully a super simple demonstration to reproduce this.
I would appreciate any help with this.
Thank you
The demonstration is composed of:
1) thrower.cpp - a source file that
2009 Jun 10
0
KDE and mounting CD's / DVD's without noexec
Hi e,
I am normally use gnome and would do the following to make my CD / DVD
mount with exec
gnome-mount --write-settings --device /dev/sdc0 -o exec
What is the equivalent in KDE ? My initial research suggests that I
actually have to write a custom udev rule to achieve this.
This has led me as far as running
udevinfo -q path -n /dev/scd0
udevtest /block/sr0 (the output is below)
My
2014 Apr 24
0
Problem making usbhid-ups working on Centos 5.7
On Apr 23, 2014, at 3:47 AM, Frantz de Germain wrote:
> I've compiled and installed nut-2.7.2 on a Xen server (Actually XCP
> 1.6/Centos 5.7) to manage a Dell UPS 2700W.
>
> Here is my ups.conf :
>
> [SU27003U-08]
> driver = usbhid-ups
> port = auto
> desc = "SU27003U-08"
>
> 52-nut-usbups.rules have well been installed in
2014 Apr 23
2
Problem making usbhid-ups working on Centos 5.7
Hello,
I've compiled and installed nut-2.7.2 on a Xen server (Actually XCP
1.6/Centos 5.7) to manage a Dell UPS 2700W.
Here is my ups.conf :
[SU27003U-08]
driver = usbhid-ups
port = auto
desc = "SU27003U-08"
52-nut-usbups.rules have well been installed in /lib/udev/rules.d/. I've put
it in /etc/udev/rules.d/ too.
I've rebooted the machine.
2015 Mar 20
2
[LLVMdev] LLVM Exception Handling
Hi,
I am trying to implement a scenario similar to running ExceptionDemo.cpp
with parameter -1 (where the JITed code calls the C++ function which throws
an exception)
Different from the given example I am using IRParser instead of IRBuilder.
I can successfully catch the exception in Linux but the program crashes in
Mac and Windows.
The code is similar to as follows:
### The test.cpp :
2010 Nov 09
0
[LLVMdev] Calling PassManager on previously JITed Modules
Hi,
I found the following wiki page in the Unladen Swallow project:
http://code.google.com/p/unladen-swallow/wiki/CodeLifecycle
This would appear to answer my question. Could someone confirm for me
if it's definitely unsafe to attempt to optimise/JIT any Modules while
a different thread is currently executing a JITed function which has
been generated from them? Or am I just missing
2010 Nov 09
1
[LLVMdev] Calling PassManager on previously JITed Modules
Hi Stephen,
I confirm your observation. AFAIK the current JIT keeps informations from
the module, for example AssertingHandle on Values.
It's part of my plan to make the MCJIT independent from Module stuff to
allow reoptimizations, or to have multiple copies of JITed functions for one
function in the module, but there is a long road to go.
Olivier.
On Tue, Nov 9, 2010 at 6:57 PM, Stephen
2010 Nov 08
3
[LLVMdev] Calling PassManager on previously JITed Modules
Hi,
Has anyone had any success with running different PassManagers on
llvm::Modules they've already JITed and are executing?
In detail:
1) getting the IR, in form of an llvm::Module
2) calling PassManager->run() on the module
3) calling getFunction() and getPointerToFunction() to JIT the module
4) executing the JITed code using the function pointer received in step 3
and then what I
2010 Mar 18
2
[LLVMdev] r98459 break of ExceptionDemo
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
2010 Mar 22
2
[LLVMdev] r98459 break of ExceptionDemo
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
2010 Apr 16
0
[LLVMdev] r98459 break of ExceptionDemo
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
2010 Mar 18
0
[LLVMdev] r98459 break of ExceptionDemo
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
2015 Aug 13
4
Linking existing functions from JITed code
Hi
I’ve previously used the ExecutionEngine::addGlobalMapping to make existing
functions available to my JITed code.
I’m currently using ORC, as MCJIT does not appear to be maintained any
longer (the kaleidoscope examples have not worked for some time with
MCJIT).
I’m using just the basic ORC CompileLayer directly.
So, I’ve essentially copied the ExecutionEngine::addGlobalMapping related
2015 Aug 13
2
Linking existing functions from JITed code
Hi Andy,
I haven't tested this on Linux, but on MacOS the
RuntimeDyldMemorManager::getSymbolAddressInProcess method should find
symbol addresses in the host program, including symbols from static
archives linked into the program. However, one gotcha is that the symbol
has to be reachable from main, otherwise the linker may strip it from the
final executable.
Do you have a test-case that I
2012 Nov 07
1
[LLVMdev] accessing personality and other exception related functions
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".
2015 Aug 20
2
Linking existing functions from JITed code
Hi Andy,
I think that makes sense. I'm currently rewriting the core Kaleidoscope
tutorials - I'll look at adding support for this.
- Lang.
On Fri, Aug 14, 2015 at 7:38 AM, Andy Somogyi <andy.somogyi at gmail.com>
wrote:
> After some fiddling with it, it does in fact look like it works as you
> describe Lang.
>
> The trick was you had to call
>
>
2015 Aug 20
2
Linking existing functions from JITed code
Lang,
I added the add/get global mapping to my kaleidoscope JIT, but I think perhaps these would make more sense if they were added to the object linking layer as they would be generally usable there.
On Aug 19, 2015, at 11:19 PM, Andy Somogyi wrote:
> Hey Lang,
>
> I've added this to my Kaleidoscope JIT, and it seems to work just fine, basically I copied the global mapping
2011 Jul 21
0
[LLVMdev] Catching exceptions passed through a JIT ExecutionEngine
On Tue, Jul 12, 2011 at 07:25:16PM -0400, Peter Zion said
> Hi All,
>
> I'm trying to catch an exception that is "passed through" an LLVM ExecutionEngine but I am unable to do so. Specifically, in C++ code, inside a try/catch block, I call a JITted function, which in turn calls back into my code. Everything works fine unless an exception is thrown; I would except the