From: Andrew Cagney <ac131313@redhat.com>
To: Corinna Vinschen <vinschen@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] xstormy16-tdep.c: Set chars to unsigned
Date: Tue, 25 Mar 2003 16:54:00 -0000 [thread overview]
Message-ID: <3E8089A9.8070805@redhat.com> (raw)
In-Reply-To: <20030325163554.GH23762@cygbert.vinschen.de>
> On Tue, Mar 25, 2003 at 11:28:45AM -0500, Andrew Cagney wrote:
>
>> Does this also fix some sizeof.exp failures? That test is ment to check
>> for this problem.
>
>
> XStormy16 has no sizeof.exp FAILs.
These tests:
print/d (int) (char) -1
$11 = -1
(gdb) PASS: gdb.base/sizeof.exp: get value of (int) (char) -1 (-1)
print/d (int) (signed char) -1
$12 = -1
(gdb) PASS: gdb.base/sizeof.exp: get value of (int) (signed char) -1 (-1)
print/d (int) (unsigned char) -1
$13 = 255
(gdb) PASS: gdb.base/sizeof.exp: get value of (int) (unsigned char) -1 (255)
next
valueof ((int) (char) -1) == -1
118 printf ("valueof ((int) (signed char) -1) == %d\n", (int)
(signed char) -1);
(gdb) PASS: gdb.base/sizeof.exp: check valueof (int) (char) -1 == -1
next
valueof ((int) (signed char) -1) == -1
119 printf ("valueof ((int) (unsigned char) -1) == %d\n", (int)
(unsigned char) -1);
(gdb) PASS: gdb.base/sizeof.exp: check valueof (int) (signed char) -1 == -1
next
valueof ((int) (unsigned char) -1) == 255
121 return 0;
(gdb) PASS: gdb.base/sizeof.exp: check valueof (int) (unsigned char) -1
== 255
are ment to ensure that GCC/target and GDB have a consistent idea the
signness of a character.
If GDB was getting char's sign wrong, but those tests were passing, then
there is a bug in that test case.
Can you please check this, and expand a little on exactly what the
charsets.exp problem was.
Andrew
next prev parent reply other threads:[~2003-03-25 16:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-25 16:18 Corinna Vinschen
2003-03-25 16:28 ` Andrew Cagney
2003-03-25 16:36 ` Corinna Vinschen
2003-03-25 16:54 ` Andrew Cagney [this message]
2003-03-25 17:07 ` Corinna Vinschen
2003-03-25 23:24 ` Andrew Cagney
2003-03-26 9:13 ` Corinna Vinschen
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=3E8089A9.8070805@redhat.com \
--to=ac131313@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=vinschen@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