From: Hans-Peter Nilsson <hp@axis.com>
To: Jonathan Wakely <jwakely@redhat.com>
Cc: <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 03:12:57 +0100 [thread overview]
Message-ID: <20231120021257.630B72041D@pchp3.se.axis.com> (raw)
In-Reply-To: <20231116172021.1344351-1-jwakely@redhat.com> (message from Jonathan Wakely on Thu, 16 Nov 2023 17:20:09 +0000)
> From: Jonathan Wakely <jwakely@redhat.com>
> Date: Thu, 16 Nov 2023 17:20:09 +0000
> PR libstdc++/112564
> * include/std/stacktrace (formatter::format): Format according
> to format-spec.
> * include/std/thread (formatter::format): Use _Align_right as
> default.
> * testsuite/19_diagnostics/stacktrace/output.cc: Check
> fill-and-align handling. Change compile test to run.
> * testsuite/30_threads/thread/id/output.cc: Check fill-and-align
> handling.
You already know this, so JFTR: this introduced a regression
for some targets, logged as PR112630.
Was this change deliberate:
> --- a/libstdc++-v3/testsuite/19_diagnostics/stacktrace/output.cc
> +++ b/libstdc++-v3/testsuite/19_diagnostics/stacktrace/output.cc
> @@ -1,4 +1,5 @@
> -// { dg-do compile { target c++23 } }
> +// { dg-options "-lstdc++exp" }
> +// { dg-do run { target c++23 } }
> // { dg-require-effective-target stacktrace }
> // { dg-add-options no_pch }
i.e. changing from dg-compile to dg-run?
I'm guessing so. Though the changelog entry and post isn't
explicit, the use of VERIFY is rather clear and most tests
in 19_diagnostics/stacktrace are dg-run.
If so, can the "dg-run-ness" of the test please move to a
separate test and let 19_diagnostics/stacktrace/output.cc be
just dg-compile? This particular test may not warrant the
consideration, but more so a pattern to follow for other
tests.
brgds, H-P
PS. Sorry, I have no idea why regarding the underlying multi-target problem
next prev parent reply other threads:[~2023-11-20 2:13 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 [this message]
2023-11-20 11:55 ` Jonathan Wakely
2023-11-20 16:18 ` Hans-Peter Nilsson
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=20231120021257.630B72041D@pchp3.se.axis.com \
--to=hp@axis.com \
--cc=gcc-patches@gcc.gnu.org \
--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).