From: "Maciej W. Rozycki" <macro@codesourcery.com>
To: Joel Brobecker <brobecker@adacore.com>,
Richard Sandiford <rdsandiford@googlemail.com>
Cc: Tristan Gingold <gingold@adacore.com>, <binutils@sourceware.org>,
<gdb-patches@sourceware.org>
Subject: Re: Release 2.24
Date: Mon, 02 Dec 2013 16:21:00 -0000 [thread overview]
Message-ID: <alpine.DEB.1.10.1311251525340.21686@tp.orcam.me.uk> (raw)
In-Reply-To: <20131125122405.GC3114@adacore.com>
On Mon, 25 Nov 2013, Joel Brobecker wrote:
> > I'm not sure who has the authority to approve this change for GDB 7.6
> > though.
>
> I suggest a quick look from the binutils maintainer who approved
> the patches on HEAD.
Richard, can you help?
> For testing, I know you showed the spectacular improvements with
> binutils 2.24. Have you tested that it doesn't change anything
> when using 2.23, by any chance? Just in the interest of being extra
> safe, I think that would be useful testing.
It took me a little while to set it up, but I have now did this testing.
I ran o32 testing only, for standard MIPS, MIPS16 and microMIPS code (GCC
multilibs). I had to tweak compiler options used in testing so as to
avoid producing code incompatible with standard MIPS PLT entries,
`-fno-optimize-sibling-calls' and `-mno-jals -fno-optimize-sibling-calls'
respectively for MIPS16 and microMIPS code. Standard MIPS code required
no extra options. There were no regressions in this setup with binutils
2.23 (the tip of binutils-2_23-branch).
Maciej
next prev parent reply other threads:[~2013-12-02 16:21 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2741C968-721F-46E9-A2BA-E4B0F64C444B@adacore.com>
[not found] ` <BB32BE2A-A3CC-494C-9FB2-CFD322F49EA3@adacore.com>
2013-09-18 20:56 ` Maciej W. Rozycki
2013-09-18 21:32 ` Joel Brobecker
2013-09-18 22:26 ` Maciej W. Rozycki
2013-09-19 12:20 ` Joel Brobecker
2013-11-18 16:58 ` Maciej W. Rozycki
2013-11-18 17:25 ` Joel Brobecker
2013-11-21 19:33 ` Maciej W. Rozycki
2013-11-22 3:02 ` Joel Brobecker
2013-11-22 3:28 ` H.J. Lu
2013-11-22 4:22 ` Joel Brobecker
2013-11-23 19:12 ` Hans-Peter Nilsson
2013-11-22 8:17 ` Joel Brobecker
2013-11-22 15:01 ` Tom Tromey
2013-11-24 10:07 ` Joel Brobecker
2013-11-25 9:49 ` Tristan Gingold
2013-11-25 9:52 ` Joel Brobecker
2013-11-25 12:19 ` Maciej W. Rozycki
2013-11-25 12:56 ` Joel Brobecker
2013-12-02 16:21 ` Maciej W. Rozycki [this message]
2013-12-02 19:51 ` Richard Sandiford
2013-12-03 2:52 ` Joel Brobecker
2013-12-06 23:55 ` Maciej W. Rozycki
2013-12-07 3:37 ` Joel Brobecker
2013-12-08 3:56 ` Joel Brobecker
2013-12-08 8:40 ` Joel Brobecker
2013-09-19 3:59 ` Jeff Law
2013-09-20 13:15 ` Michael Matz
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=alpine.DEB.1.10.1311251525340.21686@tp.orcam.me.uk \
--to=macro@codesourcery.com \
--cc=binutils@sourceware.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=gingold@adacore.com \
--cc=rdsandiford@googlemail.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