Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: manjo@austin.ibm.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC] unsigned32 and unsigned64 is multiply defined in sim-types.h.
Date: Wed, 20 Apr 2005 22:07:00 -0000	[thread overview]
Message-ID: <200504202206.j3KM6nPZ022715@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <Pine.LNX.4.58.0504200954590.20476@lazy> (message from Manoj Iyer on Wed, 20 Apr 2005 10:01:52 -0500 (CDT))

   Date: Wed, 20 Apr 2005 10:01:52 -0500 (CDT)
   From: Manoj Iyer <manjo@austin.ibm.com>

   --- src/sim/common/sim-types.h	2002-11-22 19:12:05.000000000 -0600
   +++ new/src/sim/common/sim-types.h	2005-04-20 09:52:45.000000000 -0500
   @@ -112,11 +112,11 @@ typedef struct { signed64 a[2]; } signed
    typedef signed char signed8;
    typedef signed short signed16;
    #if defined (__ALPHA__)
   -typedef signed int unsigned32;
   -typedef signed long unsigned64;
   +typedef signed int signed32;
   +typedef signed long signed64;
    #else
   -typedef signed long unsigned32;
   -typedef signed long long unsigned64;
   +typedef signed long signed32;
   +typedef signed long long signed64;
    #endif

    typedef unsigned char unsigned8;

B.t.w. this whole bit of code looks highly suspicious (but that's not
your fault Manjo).  It looks as if this implies the alpha is still the
only 64-bit architecture around.

Mark


  parent reply	other threads:[~2005-04-20 22:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-20 15:01 Manoj Iyer
2005-04-20 15:05 ` Daniel Jacobowitz
2005-04-20 15:14   ` Manoj Iyer
2005-04-20 15:26     ` Daniel Jacobowitz
2005-04-20 22:07 ` Mark Kettenis [this message]
2005-04-20 22:23   ` Manoj Iyer
2005-04-20 22:28   ` Daniel Jacobowitz

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=200504202206.j3KM6nPZ022715@elgar.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=gdb-patches@sources.redhat.com \
    --cc=manjo@austin.ibm.com \
    /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