From: Fred Fish <fnf@specifix.com>
To: gdb-patches@sourceware.org
Cc: fnf@specifix.com
Subject: Re: [RFC] Passing MIPS debug hints between gcc and gdb
Date: Tue, 13 Jun 2006 16:08:00 -0000 [thread overview]
Message-ID: <200606131210.28356.fnf@specifix.com> (raw)
In-Reply-To: <200606120611.32335.fnf@specifix.com>
On Monday 12 June 2006 06:11, Fred Fish wrote:
> OK, here is a gcc patch to do that, and a matching gdb patch to use
> it.
Anyone want to review the gdb patch? :-)
Thanks.
-Fred
next prev parent reply other threads:[~2006-06-13 16:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-10 16:05 Fred Fish
2006-05-11 6:57 ` Richard Sandiford
2006-05-11 10:16 ` Fred Fish
2006-05-17 20:32 ` Fred Fish
2006-05-18 0:04 ` Mark Mitchell
2006-05-18 16:53 ` Richard Sandiford
2006-06-12 10:10 ` Fred Fish
2006-06-12 11:07 ` Richard Sandiford
2006-06-13 16:08 ` Fred Fish [this message]
2006-06-13 17:42 ` 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=200606131210.28356.fnf@specifix.com \
--to=fnf@specifix.com \
--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