Re: GIMPLE and intent of variables

2011-08-25 Thread Mateusz Grabowski
During determining the intent of variable I run into problems with PHI nodes. The problematical GIMPLE code looks: # BLOCK 196 # PRED: 194 (false) (...) ndycD.8665_1099 = 1; # BLOCK 197 # PRED: 196 (true) 207 (false) # ndycD.8665_4 = PHI (...) # BLOC

Re: GIMPLE and intent of variables

2011-08-25 Thread Mateusz Grabowski
Mateusz Grabowski wrote: > > > If a function calls another, the intent of variables should be passed to the first one. But what if the callee is in the other compilation unit? Does anyone have knowledge of using LTO mode? > > At this moment I have many compilation units. In my case the m

Re: GIMPLE and intent of variables

2011-08-22 Thread Richard Guenther
On Mon, Aug 22, 2011 at 2:57 PM, Mateusz Grabowski wrote: > > > Richard Guenther-2 wrote: >> >> >> The latter. >> >> > > But how to do it? I want to have all functions after SSA pass, but before > any optimizations. Maybe you could tell me how to enforce it (or even better > - a small example)? >

Re: GIMPLE and intent of variables

2011-08-22 Thread Mateusz Grabowski
Richard Guenther-2 wrote: > > > The latter. > > But how to do it? I want to have all functions after SSA pass, but before any optimizations. Maybe you could tell me how to enforce it (or even better - a small example)? Thanks in advance. -- View this message in context: http://old.nabble.

Re: GIMPLE and intent of variables

2011-08-22 Thread Richard Guenther
On Mon, Aug 22, 2011 at 2:21 PM, Mateusz Grabowski wrote: > > Thank you for all the answers. Now I have another problem. > > When I reach a function call during statement iteration, I want to go to > this function's code. > > if (is_gimple_call(stmt)) { >                tree fndecl = gimple_call_f

Re: GIMPLE and intent of variables

2011-08-22 Thread Mateusz Grabowski
Thank you for all the answers. Now I have another problem. When I reach a function call during statement iteration, I want to go to this function's code. if (is_gimple_call(stmt)) { tree fndecl = gimple_call_fndecl(stmt); // This returns function_decl ;-)

Re: GIMPLE and intent of variables

2011-08-17 Thread Jeff Law
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/17/11 01:38, grabekm90 wrote: >> > > The question is: how can we get to know, using GIMPLE mechanism, from > which parameter a pointer derives? You'd have to build code to record the derivations. Ideally you'd work on the SSA graph and just re

Re: GIMPLE and intent of variables

2011-08-17 Thread Richard Guenther
On Wed, Aug 17, 2011 at 9:38 AM, grabekm90 wrote: > > > > Jeff Law wrote: >> >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> On 08/16/11 15:35, grabekm90 wrote: >> >>> How to resolve a problem with pointers (especially arrays)? For >>> example, we have a GIMPLE function: >>> >>> set_a (i

Re: GIMPLE and intent of variables

2011-08-17 Thread grabekm90
Jeff Law wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 08/16/11 15:35, grabekm90 wrote: > >> How to resolve a problem with pointers (especially arrays)? For >> example, we have a GIMPLE function: >> >> set_a (int * a) { int * D.2701; D.2701 = a + 40; *D.2701 = 7; } >> >>

Re: GIMPLE and intent of variables

2011-08-16 Thread grabekm90
Jeff Law wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 08/16/11 15:35, grabekm90 wrote: > >> How to resolve a problem with pointers (especially arrays)? For >> example, we have a GIMPLE function: >> >> set_a (int * a) { int * D.2701; D.2701 = a + 40; *D.2701 = 7; } >> >>

Re: GIMPLE and intent of variables

2011-08-16 Thread Jeff Law
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/16/11 15:35, grabekm90 wrote: > How to resolve a problem with pointers (especially arrays)? For > example, we have a GIMPLE function: > > set_a (int * a) { int * D.2701; D.2701 = a + 40; *D.2701 = 7; } > > This is equivalent code in C: > > vo