public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Steven Bosscher <stevenb.gcc@gmail.com>
To: Georg-Johann Lay <avr@gjlay.de>
Cc: gcc-patches@gcc.gnu.org, Denis Chertykov <chertykov@gmail.com>,
		Eric Weddington <eric.weddington@atmel.com>
Subject: Re: [Patch,AVR]: Hack around PR rtl-optimization/52543, Take #2
Date: Tue, 20 Mar 2012 20:06:00 -0000	[thread overview]
Message-ID: <CABu31nPoMwSGT6BGvhv1XFk91gkWi927eJ_y7BbXgUEzBnXqmA@mail.gmail.com> (raw)
In-Reply-To: <4F68E062.5040202@gjlay.de>

On Tue, Mar 20, 2012 at 8:54 PM, Georg-Johann Lay <avr@gjlay.de> wrote:
> Dropping the first patch which does not work because at expand-time there
> must not be pre-/post-modify addressing :-(

Have you tried to fix that, instead? Or at least ask around a bit to
see what people would think about that idea? The reasons why things
are the way they are, may not be applicable anymore.

For example, perhaps the only reason for not having pre-/post-modify
addressing modes earlier is that the old "flow" dataflow frame work
didn't handle them. And it doesn't seem to be so black-and-white: The
very pass you ran into problems with first, cprop, does handle
pre-/post-modify addresses in local cprop. Some other passes simply
take the conservative path and drop pre-/post-modify (like CSE, which
doesn't record values from them). It may be a relatively small job to
make everything accept them, and you may be something that's also
helpful for other targets.

Ciao!
Steven

  parent reply	other threads:[~2012-03-20 20:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-09 18:47 [Patch,AVR]: Hack around PR rtl-optimization/52543 Georg-Johann Lay
2012-03-19 11:25 ` Ping #1: " Georg-Johann Lay
2012-03-19 11:36   ` Denis Chertykov
2012-03-19 17:29 ` Mike Stump
2012-03-20 19:54 ` [Patch,AVR]: Hack around PR rtl-optimization/52543, Take #2 Georg-Johann Lay
2012-03-20 19:56   ` Georg-Johann Lay
2012-03-21 11:47     ` Weddington, Eric
2012-03-20 20:06   ` Steven Bosscher [this message]
2012-03-21 14:03     ` Georg-Johann Lay

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=CABu31nPoMwSGT6BGvhv1XFk91gkWi927eJ_y7BbXgUEzBnXqmA@mail.gmail.com \
    --to=stevenb.gcc@gmail.com \
    --cc=avr@gjlay.de \
    --cc=chertykov@gmail.com \
    --cc=eric.weddington@atmel.com \
    --cc=gcc-patches@gcc.gnu.org \
    /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).