From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 0C673385783F; Mon, 2 Oct 2023 01:39:43 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 0C673385783F DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1696210783; bh=75lPoWCjCgMG3MoUFynimhbRxmdYqPqr/3R06QN6lv4=; h=From:To:Subject:Date:In-Reply-To:References:From; b=TjUKXMze8KzEoSR/Q2RaB1AnSaxBC79AOCnR1XbJofYfO+/WynG5C30dzV69ESPu6 HmmmCHDvvWEtBGLPwGZNYDebqnDaz3zt6BNiYUuzXlCMtUIipnDvLmCib+o694Tfxv iIN8cFkkn00JQ3bGvDSXq0AKvUTzLRvUMunbEHuc= From: "envia at envia dot pe.kr" 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 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 14.0 X-Bugzilla-Keywords: compile-time-hog X-Bugzilla-Severity: normal X-Bugzilla-Who: envia at envia dot pe.kr X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 14.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D111660 --- Comment #9 from Hwang Joonhyung --- (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=3Dgnu++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. >=20 > Does -fno-checking solve the performance issue? No. It took almost the same time. I used -std=3Dgnu++2a -fno-checking.=