From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-patches-return-294603-listarch-gcc-patches=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 12626 invoked by alias); 16 Jun 2011 19:17:43 -0000
Received: (qmail 12614 invoked by uid 22791); 16 Jun 2011 19:17:42 -0000
X-SWARE-Spam-Status: No, hits=-2.4 required=5.0	tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST
X-Spam-Check-By: sourceware.org
Received: from mail-ey0-f175.google.com (HELO mail-ey0-f175.google.com) (209.85.215.175)    by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 16 Jun 2011 19:17:26 +0000
Received: by eye27 with SMTP id 27so764776eye.20        for <gcc-patches@gcc.gnu.org>; Thu, 16 Jun 2011 12:17:25 -0700 (PDT)
Received: by 10.14.99.71 with SMTP id w47mr518624eef.221.1308251845167; Thu, 16 Jun 2011 12:17:25 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.14.186.16 with HTTP; Thu, 16 Jun 2011 12:17:05 -0700 (PDT)
In-Reply-To: <4DFA48FA.8010904@redhat.com>
References: <4DF0FAB5.6070704@gjlay.de> <BANLkTi=1v9KGgCL0V0+i=LOtbCh51FLm+A@mail.gmail.com> <4DF11D20.4030907@gjlay.de> <BANLkTi=VAo8UcLDsvBp5vWk3qaO5RQvAKg@mail.gmail.com> <4DF1ED76.4030507@gjlay.de> <BANLkTi=P0zopComgS6FDZ=cg3s9sDuKNHg@mail.gmail.com> <4DF650B7.3030705@gjlay.de> <BANLkTimPjxMw48oExFWLtDcdB=3nb_VH0g@mail.gmail.com> <4DF73490.2080709@gjlay.de> <BANLkTim=EZDDtSxpE0b0aU7wjcxynsyUqg@mail.gmail.com> <4DF7D2B5.1090708@gjlay.de> <4DF8ED42.1030706@redhat.com> <4DF918A9.4070003@gjlay.de> <4DF92AEA.4000906@redhat.com> <4DF93B17.8020008@redhat.com> <BANLkTinHp6srsLutLeE1dKDM1gutDYAhkQ@mail.gmail.com> <BANLkTimOSgx70S=wM+8EMT8DacHfjmr8zA@mail.gmail.com> <4DFA0C13.9060102@redhat.com> <BANLkTi=w8AT714QZeES6=UcPrJdgTUEVgA@mail.gmail.com> <4DFA48FA.8010904@redhat.com>
From: Denis Chertykov <chertykov@gmail.com>
Date: Thu, 16 Jun 2011 19:33:00 -0000
Message-ID: <BANLkTinZgkiurSPi+vubTuB+bUSc_SVMpg@mail.gmail.com>
Subject: Re: [Patch, AVR]: Fix PR46779
To: Richard Henderson <rth@redhat.com>
Cc: Georg-Johann Lay <avr@gjlay.de>, gcc-patches@gcc.gnu.org, Anatoly Sokolov <aesok@post.ru>, 	"Eric B. Weddington" <eric.weddington@atmel.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-patches.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-patches/>
List-Post: <mailto:gcc-patches@gcc.gnu.org>
List-Help: <mailto:gcc-patches-help@gcc.gnu.org>
Sender: gcc-patches-owner@gcc.gnu.org
X-SW-Source: 2011-06/txt/msg01288.txt.bz2

2011/6/16 Richard Henderson <rth@redhat.com>:
> On 06/16/2011 11:09 AM, Denis Chertykov wrote:
>> Only one question why you removed avr_legitimize_address ?
>
> It doesn't actually do anything useful.
>
> All it does is, for a subset of inputs, force the address into
> a register. =C2=A0This is the same as the fallback action. =C2=A0That is,
> any non-legitimate address is forced into a register.
>
> A more useful version of legitimize_address would be to split
> a large offset into two pieces, the large one to be CSE'd and
> the small one that fits into a memory offset.
>
> E.g. the following with which I was experimenting.

Are you working in public git repository ?
Can I chekout it ?

If not then may be you can drop a full patch against svn.

Denis.