From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Doug Evans <dje@google.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>,
"libstdc++" <libstdc++@gcc.gnu.org>
Subject: Re: [PATCH] libstdc++: Fix list.cc xmethods test.
Date: Wed, 29 Apr 2015 16:18:00 -0000 [thread overview]
Message-ID: <CAH6eHdSW7Q4SH6nMLR7scQOicEd4OR77x5BhWxTHB0mpnO80Jg@mail.gmail.com> (raw)
In-Reply-To: <CADPb22TXmpaGgwOiMwU1+E==8ouzw_xyoP3EH_An4wpp4075zQ@mail.gmail.com>
On 29 April 2015 at 17:04, Doug Evans wrote:
> Tested the same patch on the gcc 5.0 branch.
> Just double checking ... ok to apply there too?
Yes, OK for the branch too.
> btw, the test is currently marked as unsupported by the test run.
> I don't know what would be involved in marking it as failing instead,
> but I noticed this happening a lot while I was working with this code.
> I can imagine more failures going unnoticed because of this.
That's due to:
(*): Shared library is missing debugging information.^M
skipping: (*): Shared library is missing debugging information.^M
list.gdb:10: Error in sourced command file:^M
Cannot evaluate function -- may be inlined^M
skipping: list.gdb:10: Error in sourced command file:^M
skipping: Cannot evaluate function -- may be inlined^M
UNSUPPORTED: libstdc++-xmethods/list.cc
But I can't say anything more useful than that.
WARNING: multiple messages have this Message-ID
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Doug Evans <dje@google.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>,
"libstdc++" <libstdc++@gcc.gnu.org>
Subject: Re: [PATCH] libstdc++: Fix list.cc xmethods test.
Date: Wed, 29 Apr 2015 16:33:00 -0000 [thread overview]
Message-ID: <CAH6eHdSW7Q4SH6nMLR7scQOicEd4OR77x5BhWxTHB0mpnO80Jg@mail.gmail.com> (raw)
Message-ID: <20150429163300.v_7mDoYwGx1-RtIf5LLjLcXSRV_PX2Ff2A2sJtyMeaY@z> (raw)
In-Reply-To: <CADPb22TXmpaGgwOiMwU1+E==8ouzw_xyoP3EH_An4wpp4075zQ@mail.gmail.com>
On 29 April 2015 at 17:04, Doug Evans wrote:
> Tested the same patch on the gcc 5.0 branch.
> Just double checking ... ok to apply there too?
Yes, OK for the branch too.
> btw, the test is currently marked as unsupported by the test run.
> I don't know what would be involved in marking it as failing instead,
> but I noticed this happening a lot while I was working with this code.
> I can imagine more failures going unnoticed because of this.
That's due to:
(*): Shared library is missing debugging information.^M
skipping: (*): Shared library is missing debugging information.^M
list.gdb:10: Error in sourced command file:^M
Cannot evaluate function -- may be inlined^M
skipping: list.gdb:10: Error in sourced command file:^M
skipping: Cannot evaluate function -- may be inlined^M
UNSUPPORTED: libstdc++-xmethods/list.cc
But I can't say anything more useful than that.
next prev parent reply other threads:[~2015-04-29 16:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-27 22:33 Doug Evans
2015-04-27 22:41 ` Jonathan Wakely
2015-04-29 16:09 ` Doug Evans
2015-04-29 16:18 ` Jonathan Wakely [this message]
2015-04-29 16:33 ` Jonathan Wakely
2015-05-01 17:02 ` Jonathan Wakely
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=CAH6eHdSW7Q4SH6nMLR7scQOicEd4OR77x5BhWxTHB0mpnO80Jg@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=dje@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@gcc.gnu.org \
/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).