From: Fred Fish <fnf@gofish.ninemoons.com>
To: drow@mvista.com (Daniel Jacobowitz)
Cc: fnf@ninemoons.com, gdb-patches@sources.redhat.com
Subject: Re: [RFA] patch for mips gdb build failure with latest gcc
Date: Wed, 07 Nov 2001 12:42:00 -0000 [thread overview]
Message-ID: <200111180658.fAI6wwM12879@gofish.ninemoons.com> (raw)
In-Reply-To: <20011118013030.A4057@nevyn.them.org> from "Daniel Jacobowitz" at Nov 18, 2001 01:30:30 AM
> may have been fixed on the trunk. How recent is your "latest" GCC?
About an hour before filing the gdb bug report, straight from the head
revision of the gcc repository. I first noticed this problem probably
a month or two ago.
-Fred
prev parent reply other threads:[~2001-11-18 7:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-07 10:37 Fred Fish
2001-11-07 10:43 ` Andrew Cagney
2001-11-07 11:31 ` Daniel Jacobowitz
2001-11-07 12:42 ` Fred Fish [this message]
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=200111180658.fAI6wwM12879@gofish.ninemoons.com \
--to=fnf@gofish.ninemoons.com \
--cc=drow@mvista.com \
--cc=fnf@ninemoons.com \
--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