This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: RFA: char is unsigned on some architectures
Eli Zaretskii <eliz@is.elta.co.il> writes:
> > 2001-12-19 Jim Blandy <jimb@redhat.com>
> >
> > * gdbarch.sh (TARGET_CHAR_SIGNED): New macro.
>
> This new macro should be documented in gdbint.texinfo, I think.
Certainly. How is this?
Index: gdbint.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdbint.texinfo,v
retrieving revision 1.48
diff -c -c -b -F'^(' -r1.48 gdbint.texinfo
*** gdbint.texinfo 2001/12/15 16:53:24 1.48
--- gdbint.texinfo 2001/12/20 09:13:22
***************
*** 3501,3506 ****
--- 3501,3517 ----
@findex TARGET_CHAR_BIT
Number of bits in a char; defaults to 8.
+ @item TARGET_CHAR_SIGNED
+ @findex TARGET_CHAR_SIGNED
+ Non-zero if @code{char} is normally signed on this architecture; zero if
+ it should be unsigned.
+
+ The ISO C standard requires the compiler to treat @code{char} as
+ equivalent to either @code{signed char} or @code{unsigned char}; any
+ character in the standard execution set is supposed to be positive.
+ Most compilers treat @code{char} as signed, but @code{char} is unsigned
+ on the IBM S/390, RS6000, and PowerPC targets.
+
@item TARGET_COMPLEX_BIT
@findex TARGET_COMPLEX_BIT
Number of bits in a complex number; defaults to @code{2 * TARGET_FLOAT_BIT}.