From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: drow@false.org
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Changes to signed char and unsigned char handling
Date: Tue, 04 Sep 2007 22:40:00 -0000 [thread overview]
Message-ID: <200709042240.l84Me9bh032691@brahms.sibelius.xs4all.nl> (raw)
In-Reply-To: <20070903175312.GM12440@caradoc.them.org> (message from Daniel Jacobowitz on Mon, 3 Sep 2007 13:53:12 -0400)
> Date: Mon, 3 Sep 2007 13:53:12 -0400
> From: Daniel Jacobowitz <drow@false.org>
>
> On Fri, Aug 24, 2007 at 09:17:57PM -0400, Daniel Jacobowitz wrote:
> > Here's option 1 instead:
> >
> > 1. Make vector types special. Treat arrays of single byte integers
> > as characters, like before, unless they occur in a vector type. This
> > is reasonable, but tricky to implement.
> >
> > It restores the historic behavior for unsigned char and signed char.
> > Only the behavior of vector registers has changed. You basically
> > never want to print these as strings, but since I had already
> > implemented print/s I kept it.
>
> Mark, did you want to look at this revised approach? I think it
> will satisfy everyone; I'd like to include it in 6.7, if so.
>
> http://sourceware.org/ml/gdb-patches/2007-08/msg00467.html
Bleah! It was my intention to test this new diff, and recheck my
sparc machine to see why your first diff caused me so many problems,
but I haven't found the time to do either.
But this diff makes much more sense to me, so feel free to get it in.
Mark
next prev parent reply other threads:[~2007-09-04 22:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-05 13:54 Daniel Jacobowitz
2007-07-06 10:33 ` Eli Zaretskii
2007-07-06 21:34 ` Daniel Jacobowitz
2007-07-07 10:04 ` Eli Zaretskii
2007-07-07 17:06 ` Daniel Jacobowitz
2007-07-06 23:26 ` Nick Roberts
2007-07-06 23:46 ` Daniel Jacobowitz
2007-08-25 1:18 ` Daniel Jacobowitz
2007-08-25 10:19 ` Eli Zaretskii
2007-09-03 17:53 ` Daniel Jacobowitz
2007-09-04 13:58 ` Joel Brobecker
2007-09-04 22:40 ` Mark Kettenis [this message]
2007-09-05 0: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=200709042240.l84Me9bh032691@brahms.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
/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