From: Hans-Peter Nilsson <hp@axis.com>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: <jwakely@redhat.com>, <libstdc++@gcc.gnu.org>, <gcc-patches@gcc.gnu.org>
Subject: Re: [committed] libstdc++: Fix aligned formatting of stacktrace_entry and thread::id [PR112564]
Date: Mon, 20 Nov 2023 17:18:42 +0100 [thread overview]
Message-ID: <20231120161842.B4ED32043D@pchp3.se.axis.com> (raw)
In-Reply-To: <CAH6eHdSO-ZYBmheAwxE2jwwVg748pNE2MtAiFbajL2jqkCc+GQ@mail.gmail.com> (message from Jonathan Wakely on Mon, 20 Nov 2023 11:55:22 +0000)
> From: Jonathan Wakely <jwakely.gcc@gmail.com>
> Date: Mon, 20 Nov 2023 11:55:22 +0000
> The changelog entry does say "Change compile test to run."
Wow, it's right there. The doh:est of doh:s on me. Sorry
for wasting your time on that.
> > PS. Sorry, I have no idea why regarding the underlying multi-target problem
>
> I have some vague speculation in PR 112541.
From comment #1:
"It appears that __stacktrace_impl::_S_current returns an
empty sequence of frames.
It's possible that all the lambda frames are inlined, or
skip+2 in stacktrace.cc causes us to skip real frames that
we should keep, or maybe libbacktrace just doesn't work on
this target."
All more or less likely, with libbacktrace not working for
three targets maybe less likely. Or more.
Anyway, if I haven't found time to look at this myself
within...say two months, I think I'll xfail it for cris-elf.
brgds, H-P
next prev parent reply other threads:[~2023-11-20 16:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-16 17:20 Jonathan Wakely
2023-11-20 2:12 ` Hans-Peter Nilsson
2023-11-20 11:55 ` Jonathan Wakely
2023-11-20 16:18 ` Hans-Peter Nilsson [this message]
2023-11-20 16:50 ` 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=20231120161842.B4ED32043D@pchp3.se.axis.com \
--to=hp@axis.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jwakely.gcc@gmail.com \
--cc=jwakely@redhat.com \
--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).