public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "nightstrike at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/110167] New: excessive compile time when optimizing std::to_array
Date: Thu, 08 Jun 2023 03:18:30 +0000	[thread overview]
Message-ID: <bug-110167-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 110167
           Summary: excessive compile time when optimizing std::to_array
           Product: gcc
           Version: 13.1.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libstdc++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: nightstrike at gmail dot com
  Target Milestone: ---

#include <array>
int f[262144]; auto g(void) { return std::to_array(f); }

(Thanks to Andrew for help reducing!)

Baseline run:

$ time g++ test.cc -std=gnu++20 -O0 -c
real    0m17.274s
user    0m16.806s
sys     0m0.119s


at -O1, 2, 3, or fast, it takes too long to ever finish.  I killed it after 15
minutes.

For the curious, that array size is 512*512.  I didn't bisect to see where it
starts to blow up.

             reply	other threads:[~2023-06-08  3:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-08  3:18 nightstrike at gmail dot com [this message]
2023-06-08  9:51 ` [Bug c++/110167] " redi at gcc dot gnu.org
2023-06-08 10:17 ` redi at gcc dot gnu.org
2023-06-08 10:21 ` redi at gcc dot gnu.org
2023-06-08 10:22 ` redi at gcc dot gnu.org
2023-06-08 11:05 ` redi at gcc dot gnu.org
2023-06-08 15:01 ` redi at gcc dot gnu.org
2023-06-08 15:09 ` redi at gcc dot gnu.org
2023-06-08 15:28 ` [Bug libstdc++/110167] " redi at gcc dot gnu.org
2023-06-08 15:30 ` [Bug libstdc++/110167] excessive compile time for std::to_array with huge arrays redi at gcc dot gnu.org
2023-06-08 15:44 ` redi at gcc dot gnu.org
2023-06-09  7:00 ` rguenth at gcc dot gnu.org
2023-06-09 12:08 ` cvs-commit at gcc dot gnu.org
2023-10-19 14:07 ` redi at gcc dot gnu.org
2024-03-12 14:17 ` cvs-commit at gcc dot gnu.org
2024-03-13  9:52 ` cvs-commit at gcc dot gnu.org
2024-03-13 10:00 ` 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-110167-4@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).