From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11936 invoked by alias); 26 Mar 2004 06:35:10 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 11929 invoked from network); 26 Mar 2004 06:35:10 -0000 Received: from unknown (HELO mail.libertysurf.net) (213.36.80.91) by sources.redhat.com with SMTP; 26 Mar 2004 06:35:10 -0000 Received: from localhost.localdomain (213.36.36.60) by mail.libertysurf.net (6.5.036) id 406033E0005C04E6; Fri, 26 Mar 2004 07:35:07 +0100 Content-Type: text/plain; charset="iso-8859-1" From: Eric Botcazou To: Barry Wealand Subject: Re: Disqualifying instructions for branch delay slot scheduling Date: Fri, 26 Mar 2004 15:28:00 -0000 User-Agent: KMail/1.4.3 Cc: gcc@gcc.gnu.org, "Kancler, Cliff" , reed@reedkotler.com, "Katyryniuk, Mike" , "Steigmeyer, Bruce" References: <40636AEB.77325951@lmco.com> In-Reply-To: <40636AEB.77325951@lmco.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <200403260740.45651.ebotcazou@libertysurf.fr> X-SW-Source: 2004-03/txt/msg01543.txt.bz2 > Can anybody quickly summarize how one would go about disqualifying > certain specific instructions for branch delay slot scheduling? Any > guidance at all would be greatly appreciated. You can define a new attribute in the .md file with define_attr, defaulting to 'false', and set it to 'true' for the problematic instructions. Then test it in the DELAY-N attribute tests of the define_delay patterns. -- Eric Botcazou