From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 1CD5B3857C69; Fri, 15 Jan 2021 21:04:18 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 1CD5B3857C69 From: "mpolacek at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/98538] [11 Regression] ICE in cp_build_qualified_type_real, at cp/tree.c:1335 Date: Fri, 15 Jan 2021 21:04:17 +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: 11.0 X-Bugzilla-Keywords: ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: mpolacek at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: nathan at gcc dot gnu.org X-Bugzilla-Target-Milestone: 11.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 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jan 2021 21:04:18 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D98538 --- Comment #8 from Marek Polacek --- (In reply to Nathan Sidwell from comment #5) > I don;t think your patch is quite right. the call afterwards is making t= he > assumption that DEPENDENT_TYPE_P is only ever set when > DEPENDENT_TYPE_P_VALID is true, and as I discovered, that is not correct. > see this code near pt.c:14899 >=20 > set_underlying_type (r); > if (TYPE_DECL_ALIAS_P (r)) > /* An alias template specialization can be dependent > even if its underlying type is not. */ > TYPE_DEPENDENT_P_VALID (TREE_TYPE (r)) =3D false; > } Right, that's what lead me to tweaking the assert to not crash for alias template specializations. But I like your patch better. > I did wonder if we should just recalculate properly there though ... >=20 > 'tis annoying that 'taking' a bug does not put it in the assigned state :( Indeed :/. Thanks for fixing this.=