On Sun, May 15, 2005 at 09:23:01AM -0600, Roger Sayle wrote:
> Probably the reason that fold_unary
> doesn't call fold_indirect_ref is precisely because it is unsafe.
Probably fold_indirect_ref way way way post-dates fold_unary.
r~
On Sun, 15 May 2005, Richard Guenther wrote:
> > Exactly which optimization do we miss by changing:
> >
> > /* *&p => p */
> > - if (lang_hooks.types_compatible_p (type, optype))
> > + if (type == optype)
> > return op;
>
> I don't know - maybe stripping sign casts. But if w
Roger Sayle wrote:
> On Sun, 15 May 2005, Richard Guenther wrote:
>
>>What can be done about this issues? First, we can use VIEW_CONVERT_EXPR
>>unconditionally in fold_indirect_ref and only break some optimizations
>>(like temp1.C). Second, we can declare fold_indirect_ref being unsafe
>>about t
On Sun, 15 May 2005, Richard Guenther wrote:
> What can be done about this issues? First, we can use VIEW_CONVERT_EXPR
> unconditionally in fold_indirect_ref and only break some optimizations
> (like temp1.C). Second, we can declare fold_indirect_ref being unsafe
> about types and deal with this
