From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22762 invoked by alias); 1 Jul 2009 01:45:23 -0000 Received: (qmail 22752 invoked by uid 22791); 1 Jul 2009 01:45:22 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 01 Jul 2009 01:45:17 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id n611jFTp031962; Tue, 30 Jun 2009 21:45:15 -0400 Received: from omfg.slc.redhat.com (vpn-225-40.phx2.redhat.com [10.3.225.40]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id n611jEvg009709; Tue, 30 Jun 2009 21:45:15 -0400 Message-ID: <4A4ABFD3.2080004@redhat.com> Date: Wed, 01 Jul 2009 01:45:00 -0000 From: Jeff Law User-Agent: Thunderbird 2.0.0.21 (X11/20090320) MIME-Version: 1.0 To: daniel tian CC: gcc@gcc.gnu.org Subject: Re: Address mode offset spill References: <121fadb80906140733g6b1eec5eg4ea945867f4affb7@mail.gmail.com> <4A36B7A3.5040403@redhat.com> <121fadb80906170302p1d11a025g8ee03ca9ab4f9347@mail.gmail.com> <4A43DB0A.80003@redhat.com> <121fadb80906252033g14bd7cc5oa1df067fa81ae4a7@mail.gmail.com> In-Reply-To: <121fadb80906252033g14bd7cc5oa1df067fa81ae4a7@mail.gmail.com> Content-Type: text/plain; charset=GB2312 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org X-SW-Source: 2009-07/txt/msg00001.txt.bz2 daniel tian wrote: >> The compiler should work with or without defining LEGITIMIZE_RELOAD_ADDRESS. >> It's often difficult to write a correct LEGITIMIZE_RELOAD_ADDRESS without >> knowing the internals of how reload works. Therefore, I strongly recommend >> first writing the port without LEGITIMIZE_RELOAD_ADDRESS -- after the port >> is working correctly you can go back and add LEGITIMIZE_RELOAD_ADDRESS to >> generate more efficient code. >> >> > > Do you mean that I should not write any reload code including > secondary reload? And if it is going to work fine, then keep working > on reload part? > You should write your secondary reload code, but not LEGITIMIZE_RELOAD_ADDRESS. After your port is working well, then define LEGITIMIZE_RELOAD_ADDRESS to optimize the code better. jeff