From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
 id 522813844045; Thu,  9 Jul 2020 18:03:26 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 522813844045
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
 s=default; t=1594317806;
 bh=R1jY1g+tMbhvEcDWqVaC4t4YIb5K7YjNFPfsyfXrza8=;
 h=From:To:Subject:Date:In-Reply-To:References:From;
 b=EZE0berC9/5cJKrqdTIgUHcDiEUhvg2g1R05RopvGx3puV/HMtblvUOiwLbVV84LP
 a1GQR3n6j/kgkfBoU3+T7pr3AAb5jyg8Jd8BOoNh9oN3hrLkXrcDibZXoaGFdG0HgA
 b7VF/kpsfw7P9ihYcAlf4D99pmg8l2Ddez/BkCoA=
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/96137] [11 Regression] GCC hang on in invalid function
 definition
Date: Thu, 09 Jul 2020 18:03:26 +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: compile-time-hog
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 11.0
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cf_reconfirmed_on bug_status target_milestone
 keywords cc assigned_to everconfirmed
Message-ID: <bug-96137-4-iqmJq6COXu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-96137-4@http.gcc.gnu.org/bugzilla/>
References: <bug-96137-4@http.gcc.gnu.org/bugzilla/>
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 <gcc-bugs.gcc.gnu.org>
List-Unsubscribe: <http://gcc.gnu.org/mailman/options/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-request@gcc.gnu.org?subject=help>
List-Subscribe: <http://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jul 2020 18:03:26 -0000

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

Marek Polacek <mpolacek at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|                            |2020-07-09
             Status|UNCONFIRMED                 |ASSIGNED
   Target Milestone|---                         |11.0
           Keywords|                            |compile-time-hog
                 CC|                            |mpolacek at gcc dot gnu.org
           Assignee|unassigned at gcc dot gnu.org      |mpolacek at gcc dot=
 gnu.org
     Ever confirmed|0                           |1

--- Comment #2 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Started with my:
r11-86-gef3479afc5ab415f00a53fc6f6a990df7f6a0747

(In reply to Haoxin Tu from comment #1)
> Also, I want to know are those cases (invalid code but makes GCC hang on)
> worth reporting? If those cases can help improve the GCC FE or its
> performance, I will continue to file more reports. Otherwise, I will just
> stop doing that.

I would treat them just like ICEs.  They are useful if the testcase isn't
complete garbage.  This one is sort of useful because it shows that my chan=
ge
above has a corner case that I didn't consider.=