public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hp at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/113175] [14 Regression] testsuite/std/ranges/iota/max_size_type.cc 5x times slower
Date: Sat, 30 Dec 2023 22:48:23 +0000	[thread overview]
Message-ID: <bug-113175-4-1MWiYeyVoN@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113175-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Hans-Peter Nilsson <hp at gcc dot gnu.org> ---
Bisecting (native) has progressed beyond the r13 mark, i.e. this is indeed a
"[14 Regression]" only.

  parent reply	other threads:[~2023-12-30 22:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-30  0:36 [Bug target/113175] New: [14 Regression] MMIX: " hp at gcc dot gnu.org
2023-12-30 18:01 ` [Bug libstdc++/113175] [14 Regression] " hp at gcc dot gnu.org
2023-12-30 22:48 ` hp at gcc dot gnu.org [this message]
2023-12-31 16:49 ` [Bug testsuite/113175] " hp at gcc dot gnu.org
2023-12-31 17:08 ` xry111 at gcc dot gnu.org
2023-12-31 17:16 ` hp at gcc dot gnu.org
2023-12-31 21:47 ` redi at gcc dot gnu.org
2023-12-31 21:52 ` redi at gcc dot gnu.org
2024-01-02 17:06 ` [Bug testsuite/113175] [11/12/13/14 " ppalka at gcc dot gnu.org
2024-01-02 17:21 ` ppalka at gcc dot gnu.org
2024-01-03  2:31 ` cvs-commit at gcc dot gnu.org
2024-01-03 15:29 ` cvs-commit at gcc dot gnu.org
2024-01-03 16:00 ` cvs-commit at gcc dot gnu.org
2024-01-03 16:04 ` cvs-commit at gcc dot gnu.org
2024-01-03 16:04 ` ppalka 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-113175-4-1MWiYeyVoN@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).