Displaying 9 results from an estimated 9 matches for "function_ptr".
2002 Dec 06
2
[LLVMdev] Tarjan+function_ptrs == trouble ? (fwd)
Dear LLVM,
Recently I incorporated code into my project such that function pointers
were supported, however it seems that the TarjanSCC_iterator no longer
works on the call graph... main() is no longer reached while the function
pointers are... I can provide code, but I have a feeling there is a
simple fix... Has anyone gone through this?
Thanks,
Dave
2002 Dec 06
0
[LLVMdev] Tarjan+function_ptrs == trouble ? (fwd)
> Recently I incorporated code into my project such that function pointers
> were supported, however it seems that the TarjanSCC_iterator no longer
> works on the call graph... main() is no longer reached while the function
> pointers are... I can provide code, but I have a feeling there is a
> simple fix... Has anyone gone through this?
I'll need some more details before I
2002 Dec 06
0
[LLVMdev] Tarjan+function_ptrs == trouble ?
> if you take the time to print out the function each non-looping node iter
> traverses, it never reaches main...
Ok, first note that the CallGraph class does really stupid (but correct)
things for function pointers, so you're not going to see anything
remarkably nice here... Make sure to read the CallGraph.h comments to
understand exactly what is going on.
Despite that, I can verify
2002 Dec 06
1
[LLVMdev] Tarjan+function_ptrs == trouble ?
Thanks,
I've been through the documentation, and if I visit main, i think
everything will turn out correctly... Printing out the Call graph reveals
that main is calling this external node i think you are making reference
to. Could this be the problem?
Dave
On Fri, 6 Dec 2002, Chris Lattner wrote:
> > if you take the time to print out the function each non-looping node iter
>
2002 Dec 06
3
[LLVMdev] Tarjan+function_ptrs == trouble ? (fwd)
Test Cases:
(attached)
Iteration code:
(...)
typedef TarjanSCC_iterator<CallGraph*> MyTarjan;
CallGraph& callGraph = getAnalysis<CallGraph>();
MyTarjan iter = tarj_begin(&callGraph);
MyTarjan end = tarj_end(&callGraph);
while(iter!=end)
iter++;
(...)
if you take the time to print out the function each non-looping node iter
traverses, it never reaches main...
2013 Jul 18
0
[LLVMdev] Proposal: function prefix data
...It would look something like:
| Prefix Data ... (variable length) | Prefix Data Length (fixed length
[32 bits?]) | Function code .... |
^ function symbol points here (function code)
I hope the simple ASCII art makes it through my mail client.
To access the data, you do
prefix_data = function_ptr - sizeof(prefix_length) - prefix_length
Cheers,
Jevin
2002 Dec 06
1
[LLVMdev] WRT: function pointers + DSG
...c 2002, Vikram Adve wrote:
> P.S. I have also updated the CSIL tree. Just check out
> TarjanSCCIterator.h.
>
> --Vikram
> http://www.cs.uiuc.edu/~vadve
>
>
> > From: David Crowe <dcrowe at tremor.crhc.uiuc.edu>
> > Subject: [LLVMbugs] Re: [LLVMdev] Tarjan+function_ptrs == trouble ?
> > Sender: llvmbugs-admin at cs.uiuc.edu
> > Date: Fri, 6 Dec 2002 00:54:41 -0600 (CST)
> >
> > Thanks,
> >
> > I've been through the documentation, and if I visit main, i think
> > everything will turn out correctly... Printing out t...
2013 Jul 18
3
[LLVMdev] Proposal: function prefix data
...ta ... (variable length) | Prefix Data Length (fixed length
> [32 bits?]) | Function code .... |
>
> ^ function symbol points here (function code)
>
> I hope the simple ASCII art makes it through my mail client.
>
> To access the data, you do
>
> prefix_data = function_ptr - sizeof(prefix_length) - prefix_length
>
> Cheers,
> Jevin
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>
-------------- next par...
2013 Jul 18
6
[LLVMdev] Proposal: function prefix data
Hi,
I would like to propose that we introduce a mechanism in IR to allow
arbitrary data to be stashed before a function body. The purpose of
this would be to allow additional data about a function to be looked
up via a function pointer. Two use cases come to mind:
1) We'd like to be able to use UBSan to check that the type of the
function pointer of an indirect function call matches the