From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christopher Li Subject: Re: [PATCH 0/2] Fix sparc64 and x86_64 issues Date: Mon, 10 Aug 2009 10:49:52 -0700 Message-ID: <70318cbf0908101049v5958c121s320a5528d8fae032@mail.gmail.com> References: <70318cbf0908061416o1956a2f6vce8f17d59e8b5f78@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: Received: from mail-vw0-f172.google.com ([209.85.212.172]:54776 "EHLO mail-vw0-f172.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932376AbZHJRtv (ORCPT ); Mon, 10 Aug 2009 13:49:51 -0400 Received: by vws2 with SMTP id 2so2833652vws.4 for ; Mon, 10 Aug 2009 10:49:52 -0700 (PDT) In-Reply-To: <70318cbf0908061416o1956a2f6vce8f17d59e8b5f78@mail.gmail.com> Sender: linux-sparse-owner@vger.kernel.org List-Id: linux-sparse@vger.kernel.org To: Blue Swirl Cc: linux-sparse@vger.kernel.org On Thu, Aug 6, 2009 at 2:16 PM, Christopher Li wrote: > On Thu, Aug 6, 2009 at 1:23 PM, Blue Swirl wrote: >> On Wed, Aug 5, 2009 at 9:51 PM, Blue Swirl wrote: >>> Hi, >>> >>> With these patches, I can run Sparse on OpenBIOS sources (which use >>> libgcc) also when compiling for 64 bit targets. 64 bit targets use 128 >>> bit double cells, just like 64 bit double cells are used on 32 bit >>> targets. >>> >>> I'm not sure if 'long long long' is actually used, libgcc uses >>> __attribute__ ((mode (TI))). > > The change looks reasonable. > > I feel that we can use: > > #define MOD_ALL_LONG (MOD_LONG | MOD_LONGLONG | MOD_LONGLONGLONG) > I push the change does that. Please verify. Thanks Chris