From: Daniel Jacobowitz <drow@false.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: manjo@austin.ibm.com, gdb-patches@sources.redhat.com
Subject: Re: [RFC] unsigned32 and unsigned64 is multiply defined in sim-types.h.
Date: Wed, 20 Apr 2005 22:28:00 -0000 [thread overview]
Message-ID: <20050420222750.GA705@nevyn.them.org> (raw)
In-Reply-To: <200504202206.j3KM6nPZ022715@elgar.sibelius.xs4all.nl>
On Thu, Apr 21, 2005 at 12:06:49AM +0200, Mark Kettenis wrote:
> 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.
It's also in a not-GNUC and not-MSVC block. I doubt any of this works
especially well - although as a point of interest to Manoj, it probably
won't work on xlC if xlC supports PPC64.
--
Daniel Jacobowitz
CodeSourcery, LLC
prev parent reply other threads:[~2005-04-20 22:28 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
2005-04-20 22:23 ` Manoj Iyer
2005-04-20 22:28 ` Daniel Jacobowitz [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=20050420222750.GA705@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=manjo@austin.ibm.com \
--cc=mark.kettenis@xs4all.nl \
/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