Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: drow@false.org, gdb-patches@sources.redhat.com
Subject: Re: [rfa] C++ testsuite fix for unsigned char
Date: Sat, 28 Feb 2004 23:15:00 -0000	[thread overview]
Message-ID: <20040228231519.73C424B104@berman.michael-chastain.com> (raw)

Approved, provided that you've tested it at least once.

> By the way, this test would be invalid C since it relies on the behavior of
> signed overflow.  I'm not sure about C++ but I suspect it's the same.

You are right.  It would be okay with me to change all the 'c' from
'char' to 'unsigned char'.  It's about templates, not about whether
chars are 'signed' or 'unsigned'.

Michael C

===

2004-02-28  Daniel Jacobowitz  <drow@mvista.com>

	* gdb.cp/ctti.exp: Handle unsigned char type.


             reply	other threads:[~2004-02-28 23:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-28 23:15 Michael Elizabeth Chastain [this message]
2004-02-29 17:10 ` Daniel Jacobowitz
  -- strict thread matches above, loose matches on Subject: below --
2004-02-29 22:15 Michael Elizabeth Chastain
2004-02-29 22:35 ` Daniel Jacobowitz
2004-02-28 17:51 Daniel Jacobowitz

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=20040228231519.73C424B104@berman.michael-chastain.com \
    --to=mec.gnu@mindspring.com \
    --cc=drow@false.org \
    --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