From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4960 invoked by alias); 14 Feb 2007 19:52:09 -0000 Received: (qmail 4952 invoked by uid 22791); 14 Feb 2007 19:52:08 -0000 X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 14 Feb 2007 19:52:00 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.13.1/8.13.1) with ESMTP id l1EJpwXa032174; Wed, 14 Feb 2007 14:51:58 -0500 Received: from potter.sfbay.redhat.com (potter.sfbay.redhat.com [172.16.27.15]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id l1EJpq9b002026; Wed, 14 Feb 2007 14:51:52 -0500 Received: from [10.11.14.175] (vpn-14-175.rdu.redhat.com [10.11.14.175]) by potter.sfbay.redhat.com (8.12.11.20060308/8.12.11) with ESMTP id l1EJpnVP029418; Wed, 14 Feb 2007 14:51:50 -0500 Message-ID: <45D36856.8010208@redhat.com> Date: Wed, 14 Feb 2007 19:52:00 -0000 From: Dave Brolley User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050317) MIME-Version: 1.0 To: Joern Rennecke CC: "Frank Ch. Eigler" , cgen@sources.redhat.com Subject: Re: delayed branches and zero overhead loops References: <20070213153717.GA12710@elsdt-razorfish.arc.com> <20070213185118.GA20088@redhat.com> <20070213205905.GB16492@elsdt-razorfish.arc.com> <20070213211152.GD20088@redhat.com> <20070213222044.GA31512@elsdt-razorfish.arc.com> <45D34205.9000209@redhat.com> <20070214182926.GA18550@elsdt-razorfish.arc.com> In-Reply-To: <20070214182926.GA18550@elsdt-razorfish.arc.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cgen-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cgen-owner@sourceware.org X-SW-Source: 2007-q1/txt/msg00049.txt.bz2 Joern Rennecke wrote: >On Wed, Feb 14, 2007 at 12:08:21PM -0500, Dave Brolley wrote: > > >>Joern Rennecke wrote: >> >> >> >>>I which that were the case. Try to generate the decoder for the attached >>>file; it warns about one alledged Decoder ambiguity for j_L_r_r >>>[$RC-noilink] >>>versus j_L_r_r [$RC-ilink] . The values for $RC-ilink and $RC-noilink are >>>disjoint. I've also tried to use a decode-split on this problem, but to >>>no avail. >>> >>> >>> >>The problem is that RC-ilink and RC-noilink are operands. They do not >>participate in insn decoding. If there are no other differences in the >>fixed fields of the insns (it's hard to tell because of the complexity >>of your pmacros), >> >> > >That is indeed the case. The only format differences are in the >RC-ilink / RC-noilink operand and in the F0 / F1F operand. > > If so, then there must be more bits which are constant in each of the two forms of the insn, otherwise, how does the hardware decode them? >It's the same situation with long immediates. They are indicated by a >special value in any one of three operand fields. > > Then this special value should be part of the fixed bits in the insn description >If I want to know the expansion of a single macro, I find it more useful >to use pmacro-expand interactively - the latency is also much lower than >to rm -rf the entire build tree and then rebuilding. > >Speaking of which, is there a better way? I've tried deleting individual >generated files or stamps, and some clean targets, but make always >floundered. > > Usualy deleting the stamp-* files does the trick for me. Dave