https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108226
--- Comment #2 from Martin Jambor <jamborm at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #1)
>
> so somehow the restrict qualification pessimizes IPA-CP?! Martin?
>
Well, funny thing. Without restrict, IPA-CP sees (from release_ssa dump):
void Func3 (char * p1, int * p2)
{
<bb 2> [local count: 1073741824]:
*p1_3(D) = 123;
*p2_2(D) = 1;
Func1 (p1_3(D), p2_2(D));
return;
}
But with restrict in Func2 parameters, Func3 becomes:
void Func3 (char * p1, int * p2)
{
<bb 2> [local count: 1073741824]:
*p2_2(D) = 1;
*p1_4(D) = 123;
Func1 (p1_4(D), p2_2(D));
return;
}
And the different ordering of the two stores is the problem, even when
p1 is not a char pointer, because we dont't trust the types of the
actual/formal parameters for TBAA (we would need to know in what types
they are read in Func1).
