From: Lars Brinkhoff <lars.spam@nocrew.org>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Jim Blandy <jimb@cygnus.com>, gdb-patches@sources.redhat.com
Subject: Re: RFA: char is unsigned on some architectures
Date: Thu, 20 Dec 2001 00:44:00 -0000 [thread overview]
Message-ID: <85pu5as2mw.fsf@junk.nocrew.org> (raw)
In-Reply-To: <3C21194D.4090605@cygnus.com>
Andrew Cagney <ac131313@cygnus.com> writes:
> > ISO C specifies that `char' acts like either `signed char' or
> > `unsigned char'. At the moment, GDB assumes that `char' is `signed
> > char'. This patch allows the architecture to specify the correct
> > answer, and sets the value correctly for the IBM S/390 architecture.
> > 2001-12-19 Jim Blandy <jimb@redhat.com>
> > * gdbarch.sh (TARGET_CHAR_SIGNED): New macro.
> > * gdbarch.c, gdbarch.h: Regenerated.
> > * gdbtypes.c (build_gdbtypes): If TARGET_CHAR_SIGNED is zero,
> > set the TYPE_FLAG_UNSIGNED bit on the type.
> > * s390-tdep.c (s390_gdbarch_init): On the S/390, characters
> > are unsigned by default.
>
> Hmm, the rs6000 and prodogy (Hmm, IBM ...) are also unsigned.
How about ARM?
--
Lars Brinkhoff http://lars.nocrew.org/ Linux, GCC, PDP-10
Brinkhoff Consulting http://www.brinkhoff.se/ programming
next prev parent reply other threads:[~2001-12-20 8:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-19 14:43 Jim Blandy
2001-12-19 14:48 ` Andrew Cagney
2001-12-19 19:11 ` Jim Blandy
2001-12-19 19:26 ` Jim Blandy
2001-12-20 0:44 ` Lars Brinkhoff [this message]
2001-12-20 12:24 ` Jim Blandy
2002-01-07 9:13 ` Richard Earnshaw
2001-12-19 23:04 ` Eli Zaretskii
2001-12-20 1:14 ` Jim Blandy
2001-12-20 3:10 ` Eli Zaretskii
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=85pu5as2mw.fsf@junk.nocrew.org \
--to=lars.spam@nocrew.org \
--cc=ac131313@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@cygnus.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