From: Thomas Schwinge <thomas@codesourcery.com>
To: "Maciej W. Rozycki" <macro@codesourcery.com>,
David Daney <ddaney@caviumnetworks.com>
Cc: binutils@sourceware.org,
Jan Kratochvil <jan.kratochvil@redhat.com>,
Andrew Stubbs <ams@codesourcery.com>,
gdb@sourceware.org, Nathan Sidwell <nathan@codesourcery.com>
Subject: Re: MIPS: 64-bit DWARF
Date: Fri, 16 Jul 2010 11:22:00 -0000 [thread overview]
Message-ID: <871vb3r7r7.fsf@dirichlet.schwinge.homeip.net> (raw)
In-Reply-To: <alpine.DEB.1.10.1007141926271.29495@tp.orcam.me.uk>
[-- Attachment #1: Type: text/plain, Size: 1781 bytes --]
Hello!
On 2010-07-14 18:44, Maciej W. Rozycki wrote:
> On Wed, 14 Jul 2010, David Daney wrote:
>> > 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.
>>
>> How was it tested?
I developed / applied the patch using a tree with non-HEAD sources, and
(re-)built a complete mips-linux-gnu toolchain (GCC has been built with
``--enable-mips-nonpic --with-arch32=4kc --with-arch64=5kf''), then ran
all binutils and GDB regression test suites for the following multilibs
/ switches, and compared to baseline sources:
".;"
".;@mabi=64"
"mel;@mel"
"hard-float;@mhard-float"
"hard-float;@mhard-float@mabi=n32"
"hard-float;@mhard-float@mabi=64"
"hard-float/vr5500;@mhard-float@march=vr5500"
"mel/hard-float;@mel@mhard-float"
"mel/hard-float;@mel@mhard-float@mabi=n32"
"mel/hard-float;@mel@mhard-float@mabi=64"
"octeon;@march=octeon@mabi=n32"
"octeon;@march=octeon@mabi=64"
"octeon2;@march=octeon2@mabi=n32"
"octeon2;@march=octeon2@mabi=64"
"uclibc;@muclibc"
"uclibc/mel;@muclibc@mel"
>> Have you tested mips64-linux-gnu with -mabi=64?
I've now running the same testing on HEAD sources for a
mips64el-linux-gnu toolchain for:
".;"
".;@mabi=32"
".;@mabi=64"
I'll post the results once that's finished.
> The change needs to be properly tested of course to see if it does not
> uncover an odd bug somewhere, but in principle I consider it the right and
> necessary move.
Is there anything else I should be testing?
Regards,
Thomas
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2010-07-16 11:22 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 [this message]
2010-07-19 20:00 ` Richard Sandiford
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=871vb3r7r7.fsf@dirichlet.schwinge.homeip.net \
--to=thomas@codesourcery.com \
--cc=ams@codesourcery.com \
--cc=binutils@sourceware.org \
--cc=ddaney@caviumnetworks.com \
--cc=gdb@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=macro@codesourcery.com \
--cc=nathan@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).