From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6351 invoked by alias); 1 Apr 2005 10:29:25 -0000 Mailing-List: contact binutils-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: binutils-owner@sources.redhat.com Received: (qmail 6314 invoked from network); 1 Apr 2005 10:29:22 -0000 Received: from unknown (HELO mx01.qsc.de) (213.148.129.14) by sourceware.org with SMTP; 1 Apr 2005 10:29:22 -0000 Received: from port-195-158-169-58.dynamic.qsc.de ([195.158.169.58] helo=hattusa.textio) by mx01.qsc.de with esmtp (Exim 3.35 #1) id 1DHJP0-0006jB-00 for binutils@sources.redhat.com; Fri, 01 Apr 2005 12:29:22 +0200 Received: from ths by hattusa.textio with local (Exim 4.50) id 1DHJP0-000319-09 for binutils@sources.redhat.com; Fri, 01 Apr 2005 12:29:22 +0200 Date: Fri, 01 Apr 2005 10:29:00 -0000 To: binutils@sources.redhat.com Subject: Re: MIPS noreorder and nomacro Message-ID: <20050401102921.GB3566@hattusa.textio> References: <20050401020624.GA8700@nevyn.them.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050401020624.GA8700@nevyn.them.org> User-Agent: Mutt/1.5.8i From: Thiemo Seufer X-SW-Source: 2005-04/txt/msg00018.txt.bz2 Daniel Jacobowitz wrote: > The MIPS assembler currently complains about .set nomacro like so: > else if (strcmp (name, "nomacro") == 0) > { > if (mips_opts.noreorder == 0) > as_bad (_("`noreorder' must be set before `nomacro'")); > mips_opts.warn_about_macros = 1; > } > > But it will allow this: > .set noreorder > .set nomacro > ... > .set reorder > > And nothing resets warn_about_macros. So this limitation isn't very > effective; is it necessary? It makes little sense to use nomacro without noreorder. Instead of the code mentioned above, a warn_about_macros test should probably check if it is still inside a noreorder section. Thiemo