From: Simon Marchi <simon.marchi@polymtl.ca>
To: Mark Wielaard <mark@klomp.org>
Cc: Sergio Durigan Junior <sergiodj@redhat.com>,
Simon Marchi <simon.marchi@ericsson.com>,
gdb-patches@sourceware.org
Subject: Re: [PATCH 2/2] Make collect_probes return an std::vector
Date: Tue, 12 Sep 2017 11:32:00 -0000 [thread overview]
Message-ID: <334023740c848764e686314718ae45c9@polymtl.ca> (raw)
In-Reply-To: <1505210183.16423.5.camel@klomp.org>
On 2017-09-12 11:56, Mark Wielaard wrote:
> Hi,
>
> On Mon, 2017-09-11 at 20:17 -0400, Sergio Durigan Junior wrote:
>> On Sunday, September 10 2017, Simon Marchi wrote:
>> > I guess it's a bug with that specific version< of the compiler,
>> > since no other gcc gives me that error.  It is using:
>> >
>> > Â g++ (GCC) 6.3.1 20161221 (Red Hat 6.3.1-1)
>> >
>> > Any idea about this problem?
>>
>> It seems to me this is indeed a compiler problem.  I've found at
>> least one report on GCC's bugzilla about a related issue.
>>
>> Mark, you're the responsible for this specific slave
>> (marist-fedora-s390x); can you check if it's possible to update the
>> GCC there, please?
>
> It has been upgraded to gcc (GCC) 6.4.1 20170727 (Red Hat 6.4.1-1).
> marist-fedora-s390x is currently running Fedora 25. It will be updated
> in the future to Fedora 26 (which will bring an upgrade to GCC 7).
>
> Cheers,
>
> Mark
I have sent my patch to get tested on this builder, and it seems to
build fine now. Thanks to you both!
Simon
next prev parent reply other threads:[~2017-09-12 11:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-10 14:23 [PATCH 1/2] Make probe_ops::get_probes fill " Simon Marchi
2017-09-10 14:23 ` [PATCH 2/2] Make collect_probes return " Simon Marchi
2017-09-12 0:18 ` Sergio Durigan Junior
2017-09-12 9:56 ` Mark Wielaard
2017-09-12 11:32 ` Simon Marchi [this message]
2017-09-12 11:35 ` Simon Marchi
2017-09-10 17:40 ` [PATCH 1/2] Make probe_ops::get_probes fill " Sergio Durigan Junior
2017-09-10 17:59 ` Simon Marchi
2017-09-12 0:01 ` Sergio Durigan Junior
2017-09-12 11:57 ` Simon Marchi
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=334023740c848764e686314718ae45c9@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb-patches@sourceware.org \
--cc=mark@klomp.org \
--cc=sergiodj@redhat.com \
--cc=simon.marchi@ericsson.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