From: Jonathan Wakely <jwakely@redhat.com>
To: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: [committed] libstdc++: Fix FAIL: 26_numerics/random/pr60037-neg.cc again [PR113961]
Date: Fri, 16 Feb 2024 19:12:18 +0000 [thread overview]
Message-ID: <20240216191357.177511-1-jwakely@redhat.com> (raw)
In-Reply-To: <20240216105345.148641-1-jwakely@redhat.com>
I had another change to <bits/random.h> in my local tree which affected
the second dg-error and I "fixed" it unnecessarily. I've tested with a
clean tree this time.
Tested aarch64-linux. Pushed to trunk.
-- >8 --
PR libstdc++/87744
PR libstdc++/113961
libstdc++-v3/ChangeLog:
* testsuite/26_numerics/random/pr60037-neg.cc: Adjust dg-error
line number.
---
libstdc++-v3/testsuite/26_numerics/random/pr60037-neg.cc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libstdc++-v3/testsuite/26_numerics/random/pr60037-neg.cc b/libstdc++-v3/testsuite/26_numerics/random/pr60037-neg.cc
index 9d6925fb416..3c5aa7feefc 100644
--- a/libstdc++-v3/testsuite/26_numerics/random/pr60037-neg.cc
+++ b/libstdc++-v3/testsuite/26_numerics/random/pr60037-neg.cc
@@ -12,4 +12,4 @@ auto x = std::generate_canonical<std::size_t,
// { dg-error "static assertion failed: template argument must be a floating point type" "" { target *-*-* } 270 }
-// { dg-error "static assertion failed: template argument must be a floating point type" "" { target *-*-* } 3350 }
+// { dg-error "static assertion failed: template argument must be a floating point type" "" { target *-*-* } 3351 }
--
2.43.0
prev parent reply other threads:[~2024-02-16 19:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-15 11:44 [committed] libstdc++: Use 128-bit arithmetic for std::linear_congruential_engine [PR87744] Jonathan Wakely
2024-02-16 10:52 ` [committed] libstdc++: Fix FAIL: 26_numerics/random/pr60037-neg.cc [PR113931] Jonathan Wakely
2024-02-16 19:12 ` Jonathan Wakely [this message]
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=20240216191357.177511-1-jwakely@redhat.com \
--to=jwakely@redhat.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).