From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 644463858C62; Thu, 8 Jun 2023 11:05:13 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 644463858C62 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1686222313; bh=m7Vxjzr3g1dIfyAGmYlKx+Wz7HPE9nf1FxoDvVYUAHw=; h=From:To:Subject:Date:In-Reply-To:References:From; b=pFrCfE14F+eKjEYqkXf2d1gvG0qtt/N+plbjl0wcIJTMFAt8Ejaai6niUD7VZESm5 9V+PiwFNEp8YIYFNLHsV63tNC2FEYpYV9WNvh+OcJhlVHl4sRk5VQWxcxlJ3g8LFYy zkHtrSO3yOKkgHoKZjtuVY0fonQCJIOaM2+7CMYw= From: "redi at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/110167] excessive compile time when optimizing std::to_array Date: Thu, 08 Jun 2023 11:05:13 +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: 13.1.0 X-Bugzilla-Keywords: compile-time-hog X-Bugzilla-Severity: normal X-Bugzilla-Who: redi at gcc dot gnu.org 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: --- 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=3D110167 --- Comment #5 from Jonathan Wakely --- It's hard to bisect where it got slower between 10 and 11, and between 11 a= nd 12, because for --enable-checking builds the extra assertions slow everythi= ng down and the difference between "fast with slow assertions" and "slow with = slow assertions" is much less significant than "fast" and "slow".=