public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "envia at envia dot pe.kr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/111660] [14 Regression] Compilation of constexpr function returning enum takes exponential time with -std=c++2a
Date: Mon, 02 Oct 2023 01:39:42 +0000	[thread overview]
Message-ID: <bug-111660-4-teRlnwu5bo@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111660-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #9 from Hwang Joonhyung <envia at envia dot pe.kr> ---
(In reply to Andrew Pinski from comment #6)
> (In reply to Hwang Joonhyung from comment #0)
> > It took more than 30 minutes when I compiled testcase.cc with g++ 14.0.0
> > 20231001 on Debian GNU/Linux 12 with -std=gnu++2a (or gnu++20, c++2a, c++20).
> > I guess it is a regression because it finishes within 0.1 second with g++
> > 13.2.0 or 12.3.0.
> > The testcase is based on GetOneCharToken() of V8.
> 
> Does -fno-checking solve the performance issue?

No. It took almost the same time. I used -std=gnu++2a -fno-checking.

  parent reply	other threads:[~2023-10-02  1:39 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-02  1:14 [Bug c++/111660] New: " envia at envia dot pe.kr
2023-10-02  1:16 ` [Bug c++/111660] " envia at envia dot pe.kr
2023-10-02  1:17 ` envia at envia dot pe.kr
2023-10-02  1:18 ` envia at envia dot pe.kr
2023-10-02  1:24 ` envia at envia dot pe.kr
2023-10-02  1:26 ` pinskia at gcc dot gnu.org
2023-10-02  1:26 ` pinskia at gcc dot gnu.org
2023-10-02  1:31 ` pinskia at gcc dot gnu.org
2023-10-02  1:33 ` [Bug c++/111660] [14 Regression] " pinskia at gcc dot gnu.org
2023-10-02  1:39 ` envia at envia dot pe.kr [this message]
2023-10-02  2:39 ` envia at envia dot pe.kr
2023-10-02 13:34 ` ppalka at gcc dot gnu.org
2023-10-02 14:43 ` mpolacek at gcc dot gnu.org
2023-10-04  9:41 ` [Bug c++/111660] [14 Regression] Compilation of constexpr function returning enum takes exponential time with -std=c++2a since r14-4140-g6851e3423c2b5e rguenth at gcc dot gnu.org
2023-10-12 19:17 ` mpolacek at gcc dot gnu.org
2023-10-17 21:42 ` cvs-commit at gcc dot gnu.org
2023-10-17 21:43 ` mpolacek 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-111660-4-teRlnwu5bo@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).