From: Blue Swirl <blauwirbel@gmail.com>
To: Christopher Li <sparse@chrisli.org>
Cc: linux-sparse@vger.kernel.org
Subject: Re: [PATCH 0/2] Fix sparc64 and x86_64 issues
Date: Wed, 12 Aug 2009 21:42:00 +0300 [thread overview]
Message-ID: <f43fc5580908121142i207fd9di17c7070de1e74856@mail.gmail.com> (raw)
In-Reply-To: <70318cbf0908101049v5958c121s320a5528d8fae032@mail.gmail.com>
On Mon, Aug 10, 2009 at 8:49 PM, Christopher Li<sparse@chrisli.org> wrote:
> On Thu, Aug 6, 2009 at 2:16 PM, Christopher Li<sparse@chrisli.org> wrote:
>> On Thu, Aug 6, 2009 at 1:23 PM, Blue Swirl<blauwirbel@gmail.com> wrote:
>>> On Wed, Aug 5, 2009 at 9:51 PM, Blue Swirl<blauwirbel@gmail.com> 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.
Seems to work, thanks!
prev parent reply other threads:[~2009-08-12 18:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-05 18:51 [PATCH 0/2] Fix sparc64 and x86_64 issues Blue Swirl
2009-08-06 20:23 ` Blue Swirl
2009-08-06 21:16 ` Christopher Li
2009-08-10 17:49 ` Christopher Li
2009-08-12 18:42 ` Blue Swirl [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f43fc5580908121142i207fd9di17c7070de1e74856@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=linux-sparse@vger.kernel.org \
--cc=sparse@chrisli.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).