linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Blue Swirl <blauwirbel@gmail.com>
To: linux-sparse@vger.kernel.org
Subject: Re: [PATCH 0/2] Fix sparc64 and x86_64 issues
Date: Thu, 6 Aug 2009 23:23:09 +0300	[thread overview]
Message-ID: <f43fc5580908061323s61bfaf23hcbc366a74ad4de09@mail.gmail.com> (raw)
In-Reply-To: <f43fc5580908051151o560e73bdw50c3d575f50f7096@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1081 bytes --]

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))).
>
> Blue Swirl (2):
>  Add support for TImode type (__int128_t)
>  Define __LP64__ for x86_64 unless in 32 bit mode
>
>  cgcc         |    9 +++++----
>  evaluate.c   |    8 +++++---
>  expand.c     |    3 ++-
>  gdbhelpers   |    3 +++
>  parse.c      |   25 ++++++++++++++++++++++---
>  show-parse.c |    3 +++
>  symbol.c     |    6 ++++++
>  symbol.h     |    8 +++++---
>  target.c     |    1 +
>  target.h     |    1 +
>  10 files changed, 53 insertions(+), 14 deletions(-)
>

There was a bug in the 128 bit constant in cgcc, I forgot to subtract
one. Here are updated patches as attachments.

[-- Attachment #2: 0001-Add-support-for-TImode-type-__int128_t.patch --]
[-- Type: application/mbox, Size: 11274 bytes --]

[-- Attachment #3: 0002-Define-__LP64__-for-x86_64-unless-in-32-bit-mode.patch --]
[-- Type: application/mbox, Size: 913 bytes --]

  reply	other threads:[~2009-08-06 20:23 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 [this message]
2009-08-06 21:16   ` Christopher Li
2009-08-10 17:49     ` Christopher Li
2009-08-12 18:42       ` Blue Swirl

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=f43fc5580908061323s61bfaf23hcbc366a74ad4de09@mail.gmail.com \
    --to=blauwirbel@gmail.com \
    --cc=linux-sparse@vger.kernel.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).