Displaying 4 results from an estimated 4 matches for "pr1508".
Did you mean:
pr1500
2007 Dec 10
0
[LLVMdev] Darwin vs exceptions
...ector call.
In other words, you want to model LLVM's EH on the way the gcc unwinder
works. With this model indeed the inliner needs to copy the selector
to the appropriate places when inlining. Perhaps some other optimizers
need to be tweaked too. Unfortunately this approach immediately hits
PR1508 (http://llvm.org/bugs/show_bug.cgi?id=1508), i.e. the problem
of actually finding the selector for a landing pad. Personally I would
like to see the selector somehow be attached to the unwind edge - perhaps
it could be done as part of PR1269.
> > ... It is true that you can imagine a soluti...
2008 Mar 27
0
[LLVMdev] GSoC applications for vmkit
...l the time due to constructors/destructors which don't
actually do anything (but you only discover this after
having created the invoke + landing pad etc). This would
allow them to be turned into normal calls for a nice code
size reduction and code simplification.
(5) Lots of other stuff, see PR1508, PR2157 and PR2154
for starters.
Ciao,
Duncan.
2007 Dec 10
3
[LLVMdev] Darwin vs exceptions
On Dec 9, 2007, at 1:01 PM, Duncan Sands wrote:
> Hi Dale,
>
>> #include <cstdio>
>> class A {
>> public:
>> A() {}
>> ~A() {}
>> };
>> void f() {
>> A a;
>> throw 5.0;
>> }
>> main() {
>> try {
>> f();
>> } catch(...) { printf("caught\n"); }
>> }
>
> this example
2007 Dec 10
3
[LLVMdev] Darwin vs exceptions
...u, the difference
is our unwinders don't work quite the same.
> With this model indeed the inliner needs to copy the selector
> to the appropriate places when inlining. Perhaps some other
> optimizers
> need to be tweaked too. Unfortunately this approach immediately hits
> PR1508 (http://llvm.org/bugs/show_bug.cgi?id=1508), i.e. the problem
> of actually finding the selector for a landing pad. Personally I
> would
> like to see the selector somehow be attached to the unwind edge -
> perhaps
> it could be done as part of PR1269.
>
>>> ... It i...