On Fri, 30 Sep 2011, Jakub Jelinek wrote:
On Fri, Sep 30, 2011 at 10:57:25AM +0200, Richard Guenther wrote:
Definitely. Seeing a decl will enable better offset-based
disambiguation.
Ok, here is an updated patch. Bootstrapped/regtested on x86_64-linux
and i686-linux, ok for trunk?
Ok.
On Thu, 29 Sep 2011, Jakub Jelinek wrote:
Hi!
On Mon, Sep 26, 2011 at 06:41:10PM +0200, Jakub Jelinek wrote:
which would be invalid to call with foo (a, 32); given the above, but
it isn't obvious to the compiler what value y has. With -DWORKAROUND
the PT decls in (restr) look correct,
On Fri, Sep 30, 2011 at 09:50:09AM +0200, Richard Guenther wrote:
Hmm, in fwprop can you limit your change to non-invariant addresses?
That is, we do want to propagate invariant addresses over
restrict casts, because that will give us _more_ precise alias info
than restrict.
Will it?
I'd
On Fri, 30 Sep 2011, Jakub Jelinek wrote:
On Fri, Sep 30, 2011 at 09:50:09AM +0200, Richard Guenther wrote:
Hmm, in fwprop can you limit your change to non-invariant addresses?
That is, we do want to propagate invariant addresses over
restrict casts, because that will give us _more_
On Fri, Sep 30, 2011 at 10:57:25AM +0200, Richard Guenther wrote:
Definitely. Seeing a decl will enable better offset-based
disambiguation.
Ok, here is an updated patch. Bootstrapped/regtested on x86_64-linux
and i686-linux, ok for trunk?
2011-09-30 Jakub Jelinek ja...@redhat.com
Hi!
On Mon, Sep 26, 2011 at 06:41:10PM +0200, Jakub Jelinek wrote:
which would be invalid to call with foo (a, 32); given the above, but
it isn't obvious to the compiler what value y has. With -DWORKAROUND
the PT decls in (restr) look correct, without that not (supposedly because
of the
