Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Manoj Iyer <manjo@austin.ibm.com>
To: gdb-patches@sources.redhat.com
Subject: [RFC]sim/common/sim-types.h multiple defines defines?
Date: Tue, 29 Mar 2005 23:43:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.58.0503291710490.25874@lazy> (raw)


I notice in src/sim/common/sim-types.h there are multiple defines of
unsigned32 and unsigned64. I think it was intended to be signed32 and
signed64. Or am I wrong? Also, why does not gcc generate an error
message/warning for this?

The XLC compiler on AIX reports this as an error. Here is a patch that
shows what I think should be the right definitions...


--- ./sim-types.h       2005-03-29 17:18:40.000000000 -0600
+++ ./new/sim-types.h   2005-03-29 17:19:13.000000000 -0600
@@ -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;


-----
manjo
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Cogito ergo sum                                                          +
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++


                 reply	other threads:[~2005-03-29 23:43 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=Pine.LNX.4.58.0503291710490.25874@lazy \
    --to=manjo@austin.ibm.com \
    --cc=gdb-patches@sources.redhat.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