From: Sergio Durigan Junior <sergiodj@sergiodj.net>
To: Alan Modra <amodra@gmail.com>
Cc: sergiodj+buildbot@sergiodj.net, gdb-patches@sourceware.org
Subject: Re: Your commit 'PR20989, sparc GOT sequence optimisation' broke GDB
Date: Wed, 04 Jan 2017 01:16:00 -0000 [thread overview]
Message-ID: <87shozmxpd.fsf@sergiodj.net> (raw)
In-Reply-To: <20170104011148.GI31129@bubble.grove.modra.org> (Alan Modra's message of "Wed, 4 Jan 2017 11:41:48 +1030")
On Tuesday, January 03 2017, Alan Modra wrote:
> On Tue, Jan 03, 2017 at 07:20:48PM -0500, sergiodj+buildbot@sergiodj.net wrote:
>> Your commit:
>>
>> PR20989, sparc GOT sequence optimisation
>> 5b86074c4a84e32ca55a6c72c5fca45d97dc9374
>>
>> broke GDB.
>
> Unlikely. A patch for sparc breaks s390 ld?
I'll investigate. This is likely a false-positive, because I've just
re-enabled our BuildBot now after a few days offline. Sorry about that.
Thanks,
--
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/
prev parent reply other threads:[~2017-01-04 1:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1cOZJw-00067k-Ty@kwanyin.sergiodj.net>
2017-01-04 1:12 ` Alan Modra
2017-01-04 1:16 ` Sergio Durigan Junior [this message]
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=87shozmxpd.fsf@sergiodj.net \
--to=sergiodj@sergiodj.net \
--cc=amodra@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=sergiodj+buildbot@sergiodj.net \
/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