From: Michael Chastain <mec.gnu@mindspring.com>
To: jimb@redhat.com, david@streamline-computing.com, cagney@gnu.org
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH/RFA] buildsym.c: extend parent block bounds if child block exceed limit
Date: Tue, 14 Sep 2004 21:01:00 -0000 [thread overview]
Message-ID: <41475C08.nail11K212LBC@mindspring.com> (raw)
In-Reply-To: <41474D3D.4070809@gnu.org>
Andrew Cagney <cagney@gnu.org> wrote:
> Per an earlier discussion with myself and MichaelC (added to To:) its
> really important that we get testcases for this and the other fortran
> bugs in place. I'm kind of begging here :-)
Okay, I'll bump it up my priority list.
Both of these patches were to address problems with non-gcc compilers.
So I really have to develop that part first. :-/
Michael
next prev parent reply other threads:[~2004-09-14 21:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-06 21:10 David Lecomber
2004-09-14 20:00 ` Andrew Cagney
2004-09-14 20:57 ` David Lecomber
2004-09-14 21:01 ` Michael Chastain [this message]
2004-09-14 21:04 ` Daniel Jacobowitz
2004-09-14 21:21 ` David Lecomber
2004-09-20 21:30 ` Jim Blandy
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=41475C08.nail11K212LBC@mindspring.com \
--to=mec.gnu@mindspring.com \
--cc=cagney@gnu.org \
--cc=david@streamline-computing.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@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