From: Richard Sandiford <rdsandiford@googlemail.com>
To: Thomas Schwinge <thomas@codesourcery.com>
Cc: binutils@sourceware.org,
Jan Kratochvil <jan.kratochvil@redhat.com>,
Andrew Stubbs <ams@codesourcery.com>,
gdb@sourceware.org, macro@codesourcery.com,
nathan@codesourcery.com
Subject: Re: MIPS: 64-bit DWARF
Date: Mon, 19 Jul 2010 20:00:00 -0000 [thread overview]
Message-ID: <87fwzfs0mh.fsf@firetop.home> (raw)
In-Reply-To: <87eif6v450.fsf@dirichlet.schwinge.homeip.net> (Thomas Schwinge's message of "Wed, 14 Jul 2010 10:50:19 +0200")
Thomas Schwinge <thomas@codesourcery.com> writes:
> Here is the patch that I tested for (a non-HEAD version of) binutils.
> This makes prelink happy, and there are no regressions in the GDB
> testsuite. (Anything else to test?) I left in the 64-bit stuff for
> TE_IRIX, as I have no idea about it.
Patch is OK with the testing you described downstream, and with a
suitable changelog. Just to be sure, would you mind checking the
"binutils" (including gas and ld) testresults for both mips64-linux-gnu
and mips64el-linux-gnu? There's no need to test multilibs; just run
both without any test options.
Thanks,
Richard
next prev parent reply other threads:[~2010-07-19 20:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-05 12:48 debug problem with prelinked libraries Andrew Stubbs
2010-05-05 14:35 ` Daniel Jacobowitz
2010-05-05 14:59 ` Andrew Stubbs
2010-05-07 13:23 ` Jan Kratochvil
2010-05-07 13:26 ` Andrew Stubbs
2010-07-01 15:43 ` Thomas Schwinge
2010-07-06 9:59 ` MIPS: 64-bit DWARF (was: debug problem with prelinked libraries) Thomas Schwinge
2010-07-14 8:50 ` MIPS: 64-bit DWARF Thomas Schwinge
2010-07-14 16:56 ` David Daney
2010-07-14 18:44 ` Maciej W. Rozycki
2010-07-15 15:48 ` Tom Tromey
2010-07-16 14:44 ` Maciej W. Rozycki
2010-07-21 22:54 ` Joseph S. Myers
2010-07-22 5:28 ` Tom Tromey
2010-07-16 11:22 ` Thomas Schwinge
2010-07-19 20:00 ` Richard Sandiford [this message]
2010-07-22 7:41 ` Thomas Schwinge
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=87fwzfs0mh.fsf@firetop.home \
--to=rdsandiford@googlemail.com \
--cc=ams@codesourcery.com \
--cc=binutils@sourceware.org \
--cc=gdb@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=macro@codesourcery.com \
--cc=nathan@codesourcery.com \
--cc=thomas@codesourcery.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).