d
- this is infinite jumping.
Is there any option to avoid this situation?
--
View this message in context:
http://old.nabble.com/GIMPLE-and-intent-of-variables-tp32275433p32337811.html
Sent from the gcc - patches mailing list archive at Nabble.com.
ently gimple_has_body_p(fndecl) ==
NULL even if the function is in the same Fortran or C file.
--
View this message in context:
http://old.nabble.com/GIMPLE-and-intent-of-variables-tp32275433p32337494.html
Sent from the gcc - patches mailing list archive at Nabble.com.
o enforce it (or even better
> - a small example)?
> Thanks in advance.
There is no such place at the moment.
> --
> View this message in context:
> http://old.nabble.com/GIMPLE-and-intent-of-variables-tp32275433p32310942.html
> Sent from the gcc - patches mailing list archive at Nabble.com.
>
>
context:
http://old.nabble.com/GIMPLE-and-intent-of-variables-tp32275433p32310942.html
Sent from the gcc - patches mailing list archive at Nabble.com.
ment
> when the plugin is run, so that all function are already passed through SSA?
The latter.
> View this message in context:
> http://old.nabble.com/GIMPLE-and-intent-of-variables-tp32275433p32310211.html
> Sent from the gcc - patches mailing list archive at Nabble.com.
>
>
re it was passed through SSA.
Should I pass the function through SSA manually or somehow change the moment
when the plugin is run, so that all function are already passed through SSA?
--
View this message in context:
http://old.nabble.com/GIMPLE-and-intent-of-variables-tp32275433p32310211.html
-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
b8244u+6AOuVT4yVVvHJ5QGfON/UoLFUKa1SPUXRSRLKaM=
>> =HggP
>> -END PGP SIGNATURE-
>>
>>
>
> The question is: how can we get to know, using GIMPLE mechanism, from which
> parameter a pointer derives?
There are none. You can use SSA mechanisms to look up the definition
chain or use points-to information (but that doesn't give you information
about the offset).
Richard.
> --
> View this message in context:
> http://old.nabble.com/GIMPLE-and-intent-of-variables-tp32275433p32277626.html
> Sent from the gcc - patches mailing list archive at Nabble.com.
>
>
> 2UPGw3wap9SIsMEs9bG/OA13Q2WsQS7EJw2n5GH4gdlEwMmd6e8WsuQ0802SkHdX
> aVgwIJ0xQbk2RuVnRb8244u+6AOuVT4yVVvHJ5QGfON/UoLFUKa1SPUXRSRLKaM=
> =HggP
> -END PGP SIGNATURE-----
>
>
The question is: how can we get to know, using GIMPLE mechanism, from which
parameter a pointer derives?
--
View this message in context:
http://old.nabble.com/GIMPLE-and-intent-of-variables-tp32275433p32277626.html
Sent from the gcc - patches mailing list archive at Nabble.com.
> 2UPGw3wap9SIsMEs9bG/OA13Q2WsQS7EJw2n5GH4gdlEwMmd6e8WsuQ0802SkHdX
> aVgwIJ0xQbk2RuVnRb8244u+6AOuVT4yVVvHJ5QGfON/UoLFUKa1SPUXRSRLKaM=
> =HggP
> -END PGP SIGNATURE-
>
>
Yes I'd record a derived pointer but I want to notice that when it's changed
a value st
-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
sigment. Is there a simpler way?
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?
Thank you for all the answers.
--
View this message in context:
htt
12 matches
Mail list logo
