From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2003 invoked by alias); 21 Aug 2007 11:41:48 -0000 Received: (qmail 1969 invoked by uid 22791); 21 Aug 2007 11:41:47 -0000 X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (65.74.133.4) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 21 Aug 2007 11:41:42 +0000 Received: (qmail 12175 invoked from network); 21 Aug 2007 11:41:40 -0000 Received: from unknown (HELO gateway) (10.0.0.100) by mail.codesourcery.com with SMTP; 21 Aug 2007 11:41:40 -0000 Received: by gateway (Postfix, from userid 1010) id E3CEB6C0D2; Tue, 21 Aug 2007 04:41:39 -0700 (PDT) From: Richard Sandiford To: Nigel Stephens Mail-Followup-To: Nigel Stephens ,Sandra Loosemore , GCC Patches , Guy Morrogh , David Ung , Thiemo Seufer , Mark Mitchell , richard@codesourcery.com Cc: Sandra Loosemore , GCC Patches , Guy Morrogh , David Ung , Thiemo Seufer , Mark Mitchell Subject: Re: PATCH: fine-tuning for can_store_by_pieces References: <46C3343A.5080407@codesourcery.com> <87ps1nop2x.fsf@firetop.home> <46C778D6.5060808@codesourcery.com> <87y7g6r50c.fsf@firetop.home> <46CA222D.2050107@codesourcery.com> <87ps1h5mda.fsf@firetop.home> <46CABE2A.2090406@mips.com> Date: Tue, 21 Aug 2007 11:53:00 -0000 In-Reply-To: <46CABE2A.2090406@mips.com> (Nigel Stephens's message of "Tue\, 21 Aug 2007 11\:27\:54 +0100") Message-ID: <873ayd5d3g.fsf@firetop.home> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.4 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org X-SW-Source: 2007-08/txt/msg01348.txt.bz2 Nigel Stephens writes: > Richard Sandiford wrote: >> Sandra Loosemore writes: >> >>> OK, but what I was really asking was, is there a way to *test* for >>> situations where we should generate the lui/ori/sw sequences instead >>> of the lw/sw? Some combination of TARGET_foo flags and/or the size of >>> the string? >>> >> >> Well, I suppose: >> >> !optimize_size && !TARGET_MIPS16 && mips_issue_rate () > 1 > > Many MIPS dual-issue processors are asymettric, and may be able to issue > lui, ori and sw down only one pipe or the other -- not both in parallel. > So I don't think that testing mips_issue_rate() is sufficient. True. I suppose I'm biased because all the processors whose schedulers I've worked on could issue stores down one pipe and arithmetic instructions down the other. I assume you think we should stick the uncoditional zero here? Richard