From: Andrew Cagney <cagney@gnu.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: manjo@austin.ibm.com, gdb@sourceware.org
Subject: Re: Orphans to adopt?
Date: Thu, 19 May 2005 18:31:00 -0000 [thread overview]
Message-ID: <428CCFB5.5010308@gnu.org> (raw)
In-Reply-To: <200505172121.j4HLLjsi002393@elgar.sibelius.xs4all.nl>
(Hmm, remind me, what was that system I used to identify the GCC 4
gdb_byte (signed vs unsigned char) problems, that I've since been
spending my time fixing? Ah, yes ;-)
What would be immediatly helpful is for more people to expose GDB to GCC
4 so that all the other problems above and beyond gdb_byte can be
identified and fixed.
next prev parent reply other threads:[~2005-05-19 18:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-17 19:03 Stan Shebs
2005-05-17 19:07 ` Daniel Jacobowitz
2005-05-17 20:35 ` Mark Kettenis
2005-05-17 20:57 ` Manoj Iyer
2005-05-17 21:22 ` Mark Kettenis
2005-05-19 18:31 ` Andrew Cagney [this message]
2005-06-10 21:36 ` Mark Kettenis
2005-06-10 21:59 ` Manoj Iyer
[not found] <1116408555.845.ezmlm@sources.redhat.com>
2005-05-24 12:33 ` E. Weddington
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=428CCFB5.5010308@gnu.org \
--to=cagney@gnu.org \
--cc=gdb@sourceware.org \
--cc=manjo@austin.ibm.com \
--cc=mark.kettenis@xs4all.nl \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).