public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/107814] [13 regression] experimental/filesystem/iterators/error_reporting.cc FAILs
Date: Wed, 23 Nov 2022 10:05:14 +0000	[thread overview]
Message-ID: <bug-107814-4-FaHbvLmJTK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107814-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107814

--- Comment #3 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> ---
> --- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
> Are you sure this is a regression? Isn't it the same case as PR104731, but that
> was only fixed for 27_io/filesystem/iterators/error_reporting.cc and not
> experimental/filesystem/iterators/error_reporting.cc ?

I'd only checked the sparc and x86 results for the current gcc-12 branch
where the test PASSes on both.  However, the fact that the test on trunk
FAILs on x86, but PASSes on sparc seems to show that the results are
pretty unreliable.

So yea, very much looks like PR104731.

  parent reply	other threads:[~2022-11-23 10:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-22 13:32 [Bug libstdc++/107814] New: " ro at gcc dot gnu.org
2022-11-22 13:32 ` [Bug libstdc++/107814] " ro at gcc dot gnu.org
2022-11-22 13:35 ` redi at gcc dot gnu.org
2022-11-22 21:42 ` redi at gcc dot gnu.org
2022-11-23 10:05 ` ro at CeBiTec dot Uni-Bielefeld.DE [this message]
2022-11-23 10:07 ` redi at gcc dot gnu.org
2022-11-23 10:08 ` ro at CeBiTec dot Uni-Bielefeld.DE
2022-11-23 10:10 ` ro at CeBiTec dot Uni-Bielefeld.DE
2022-11-23 10:19 ` redi at gcc dot gnu.org
2022-11-23 10:20 ` cvs-commit at gcc dot gnu.org
2022-11-23 10:22 ` redi at gcc dot gnu.org
2022-12-21  9:51 ` [Bug libstdc++/107814] [10/11/12 " rguenth at gcc dot gnu.org
2022-12-21 11:37 ` cvs-commit at gcc dot gnu.org
2022-12-22 11:45 ` [Bug libstdc++/107814] [10/11 " cvs-commit at gcc dot gnu.org
2023-04-27 20:08 ` [Bug libstdc++/107814] [10 " cvs-commit at gcc dot gnu.org
2023-04-27 20:10 ` redi at gcc dot gnu.org

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=bug-107814-4-FaHbvLmJTK@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).