From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Marko Kreen" Subject: Re: confusing shift warning Date: Fri, 25 Apr 2008 17:37:01 +0300 Message-ID: References: <33544769883882222@unknownmsgid> <-3423297637585954490@unknownmsgid> <-8184754938437793631@unknownmsgid> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: Received: from nf-out-0910.google.com ([64.233.182.184]:48656 "EHLO nf-out-0910.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751430AbYDYOhC (ORCPT ); Fri, 25 Apr 2008 10:37:02 -0400 Received: by nf-out-0910.google.com with SMTP id g13so1453616nfb.21 for ; Fri, 25 Apr 2008 07:37:01 -0700 (PDT) In-Reply-To: <-8184754938437793631@unknownmsgid> Content-Disposition: inline Sender: linux-sparse-owner@vger.kernel.org List-Id: linux-sparse@vger.kernel.org To: Pavel Roskin Cc: linux-sparse@vger.kernel.org On 4/25/08, Pavel Roskin wrote: > Quoting Marko Kreen : > > On 4/25/08, Pavel Roskin wrote: > > > Quoting Marko Kreen : > > > > Patch attached. > > > > > > NACK. $m64 is only set if "-m64" was explicitly passed to cgcc. > > > > > > It looks like cgcc code expect sparse to handle it, and sparse expects > it > > > from cgcc. > > > > Do you mean the variables are not set? But they are: > > > > my $m32 = 0; > > my $m64 = 0; > > I mean, they are both 0 unless -m32 or -m64 is specified. No, see other sections - they assume one of them is set unless overrided. > > Or do you mean I cannot assume one of them as set, unless > > overrided on command line? But other sections (spact, i86, ppc) > > do exactly that? > > You cannot assume either of them to be 1 until cgcc is fixed. But how should the fix look like if you don't like mine? > > Or do you mean I cannot give extra -mXX arguement unless given by user? > > No, I don't mean it. It should be fine to add the -mXX argument. -- marko