|Dataflow and function calls email@example.com (Yuri Gribov) (2009-07-23)|
|Re: Dataflow and function calls firstname.lastname@example.org (gopi) (2009-07-28)|
|Re: Dataflow and function calls email@example.com (Yuri Gribov) (2009-07-29)|
|Re: Dataflow and function calls firstname.lastname@example.org (kamal) (2009-08-01)|
|Date:||Tue, 28 Jul 2009 06:18:47 -0700 (PDT)|
|Posted-Date:||29 Jul 2009 08:39:32 EDT|
> Now comes the question. Imagine that I want to calculate reach-defs
> via standard dataflow techniques (we use simple three-address code
> without SSA). How should I handle call instructions? Should call kill
> all definitions or keep them?
A call is handled by taking advantage of type and scope information
(local variables not impacted by call), and optionally through inter-
procedural-analysis. Where there are pointers, as a pointer (in a
language like C) can point to almost anything, optimizers make
assumptions that are controlled by command line options.
A good look at optimization and compile options (gcc will do) should
give a lot more information.
Gopi Kumar Bulusu
Sankhya Technologies Private Limited
Mobile: +91 94408 78042
Return to the
Search the comp.compilers archives again.