From: Zdenek Dvorak <rakdver@kam.mff.cuni.cz>
To: Richard Guenther <richard.guenther@gmail.com>
Cc: Ulrich Weigand <uweigand@de.ibm.com>, gcc-patches@gcc.gnu.org
Subject: Re: [patch] Fix regression (Re: Fix PR tree-optimization/41857)
Date: Tue, 17 Nov 2009 16:51:00 -0000 [thread overview]
Message-ID: <20091117164710.GA30270@kam.mff.cuni.cz> (raw)
In-Reply-To: <84fc9c000911170828x62f2e9b3ra0a0e9b26dada40a@mail.gmail.com>
Hi,
> >> >> > Tested on s390-ibm-linux and spu-elf with no regressions.
> >> >> > OK for mainline?
> >> >>
> >> >> Ugh. Â Well, good enough for now :(
> >> >>
> >> >> I think TMR is broken as it basically treats the base pointer
> >> >> as "value" compared to everywhere else where pointers have
> >> >> semantics attached (like target type, ref-all status, etc.).
> >> >
> >> > I think you paint TMRs too much evil. Â It's whole point is to be
> >> > a lower-level representation of memory access, corresponding to
> >> > the addressing modes available on the target. Â Thus, you should
> >> > expect to lose some information in the lowering.
> >>
> >> But then why try so hard and preserve TMR_ORIGINAL at all?
> >
> > because alias analysis uses it. Â Of course, another option would be to throw it
> > away completely and use some safe default. Â A better option would be to have a
> > representation of alias analysis information that would be independent on the
> > shape of the memory reference.
>
> We do have that now ...
well, almost. get_alias_set still seems to rely quite heavily on the memory reference
shape, which seems to be the only serious reason for keeping TMR_ORIGINAL at the moment
(other places where TMR_ORIGINAL are used are tree_could_trap_p, which could be solved
easily by adding a flag to TMR),
Zdenek
next prev parent reply other threads:[~2009-11-17 16:48 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-15 4:17 m32c support for named addr spaces branch DJ Delorie
2009-10-15 18:07 ` Ulrich Weigand
2009-10-15 18:11 ` DJ Delorie
2009-10-16 14:19 ` Ulrich Weigand
2009-10-16 18:22 ` DJ Delorie
2009-10-16 22:05 ` DJ Delorie
2009-10-19 14:28 ` Ulrich Weigand
2009-10-19 14:36 ` Richard Guenther
2009-10-19 17:45 ` Ulrich Weigand
2009-10-19 20:57 ` DJ Delorie
2009-10-20 9:27 ` Richard Guenther
2009-10-20 18:10 ` DJ Delorie
2009-10-21 10:20 ` Richard Guenther
2009-10-27 18:32 ` Ulrich Weigand
2009-10-28 11:29 ` Richard Guenther
2009-10-29 18:32 ` Fix PR tree-optimization/41857 (Re: m32c support for named addr spaces branch) Ulrich Weigand
2009-10-30 9:51 ` Richard Guenther
2009-11-02 9:38 ` Zdenek Dvorak
2009-11-16 20:07 ` [patch] Fix regression (Re: Fix PR tree-optimization/41857) Ulrich Weigand
2009-11-17 15:40 ` Richard Guenther
2009-11-17 16:03 ` Zdenek Dvorak
2009-11-17 16:14 ` Richard Guenther
2009-11-17 16:29 ` Zdenek Dvorak
2009-11-17 16:31 ` Richard Guenther
2009-11-17 16:51 ` Zdenek Dvorak [this message]
2009-10-30 15:55 ` m32c support for named addr spaces branch Ulrich Weigand
2009-10-16 23:57 ` DJ Delorie
2009-10-19 14:50 ` Ulrich Weigand
2009-10-29 18:37 ` [patch] Address-space-aware base registers (Re: m32c support for named addr spaces branch) Ulrich Weigand
2009-10-29 19:54 ` DJ Delorie
2009-10-29 20:18 ` DJ Delorie
2009-10-29 21:33 ` Ulrich Weigand
2009-10-29 22:50 ` DJ Delorie
2009-10-30 14:51 ` Ulrich Weigand
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20091117164710.GA30270@kam.mff.cuni.cz \
--to=rakdver@kam.mff.cuni.cz \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.guenther@gmail.com \
--cc=uweigand@de.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).