From: Tom Tromey <tromey@redhat.com>
To: Andrew Haley <aph@redhat.com>
Cc: gcc-patches@gcc.gnu.org, java-patches@gcc.gnu.org
Subject: Re: Fix Java debuginfo breakage in 4.3
Date: Thu, 06 Mar 2008 17:29:00 -0000 [thread overview]
Message-ID: <m3bq5r95cj.fsf@fleche.redhat.com> (raw)
In-Reply-To: <47CFC903.2050908@redhat.com> (Andrew Haley's message of "Thu\, 06 Mar 2008 10\:35\:47 +0000")
>>>>> "Andrew" == Andrew Haley <aph@redhat.com> writes:
Andrew> I suppose I need a test case to make sure this doesn't happen again.
Andrew> I'm not sure exactly how to write one, though.
You could look through the .S, by adding some Tcl code to special.exp
for this case. Too bad we never set up 'dg' for libjava.
Tom
next prev parent reply other threads:[~2008-03-06 17:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-06 10:36 Andrew Haley
2008-03-06 17:29 ` Tom Tromey [this message]
2008-05-23 13:51 ` Andrew Haley
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=m3bq5r95cj.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=aph@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=java-patches@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).