From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Oh dear. I regret to inform you that commit ab816a274505933da2f854014b54901c3c3db9d2 might be unfortunate
Date: Mon, 02 Oct 2017 02:43:00 -0000 [thread overview]
Message-ID: <87efqm6zhl.fsf@redhat.com> (raw)
In-Reply-To: <87h8viwbig.fsf@pokyo> (Tom Tromey's message of "Sun, 01 Oct 2017 20:04:39 -0600")
On Sunday, October 01 2017, Tom Tromey wrote:
>>>>>> "Sergio" == Sergio Durigan Junior <sergiodj@redhat.com> writes:
>
> Sergio> /usr/include/c++/4.8/bits/stl_algo.h:2245:19: error: passing
> Sergio> ‘const ada_exc_info’ as ‘this’ argument of ‘bool
> Sergio> ada_exc_info::operator<(const ada_exc_info&)’ discards
> Sergio> qualifiers [-fpermissive]
>
> I don't really understand this error, and especially why I don't see it
> (and didn't see it from try?), but I wonder if changing operator< and
> operator== to const-qualified would help.
Hm, it may be that you're not testing your patches on the AArch64
builders, maybe? At least I don't see any try builds from you here:
https://gdb-build.sergiodj.net/builders/Ubuntu-AArch64-m64?numbuilds=500
> The appended is an attempt but I'm not sure how to test it now.
You can test by specifying the AArch64 builder manually via the cli:
buildbot try -b Ubuntu-AArch64-m64
This should run the try build only on the specified builder.
--
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/
next prev parent reply other threads:[~2017-10-02 2:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5378.08408630571$1506886707@news.gmane.org>
2017-10-02 1:10 ` Sergio Durigan Junior
2017-10-02 2:04 ` Tom Tromey
2017-10-02 2:43 ` Sergio Durigan Junior [this message]
2017-10-02 9:10 ` Tejas Belagod
2017-10-02 9:39 ` Pedro Alves
2017-10-01 19:38 gdb-buildbot
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=87efqm6zhl.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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