Hi,
On Thu, Feb 17 2022, Erick Ochoa wrote:
>> If I understand you correctly, that is indeed the jump function,
>> obtainable through ipa_get_ith_jump_func (args, i) where args is a
>> result of ipa_edge_args_sum->get and i is the index of the parameter.
>>
>
> Thanks Martin!
>
> So then, am I cor
> If I understand you correctly, that is indeed the jump function,
> obtainable through ipa_get_ith_jump_func (args, i) where args is a
> result of ipa_edge_args_sum->get and i is the index of the parameter.
>
Thanks Martin!
So then, am I correct in thinking that
callsite foo -> bar
param 0: PAS
Hi,
On Thu, Feb 17 2022, Erick Ochoa wrote:
> Thanks Martin!
>
> The example I showed is simplified and I had not specified that I was using
> LTO, but I am. Thanks for asking me to clarify this.
>
> The issue I have with the information in the Lattice section of the dump is
> that it shows the in
Thanks Martin!
The example I showed is simplified and I had not specified that I was using
LTO, but I am. Thanks for asking me to clarify this.
The issue I have with the information in the Lattice section of the dump is
that it shows the information once the analysis has achieved a fixed point.
H
Hi,
On Thu, Feb 17 2022, Erick Ochoa via Gcc wrote:
> Hello,
>
> I'm trying to understand ipa-bit-cp/ipa-cp and how the known bits are
> propagated to the lattice in the case of a pointer_plus_expr.
>
> I have a piece of code similar to the following (this being a simplified
> example)
>
> int mai