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 C658838708B5; Mon, 29 Jun 2020 20:46:04 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C658838708B5
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
 s=default; t=1593463564;
 bh=PhasWBd6BI+yXs556kr16vIgxhzeJkb9nie2vbQ0yiQ=;
 h=From:To:Subject:Date:In-Reply-To:References:From;
 b=S4TmY6vtig9rdZocrnzOlc7KyN866e9XdBQZUA/gq5J7ok44ZJlEgboz+ctBKuRk0
 TKeQ+fxlcNRrmSJrVVYeLmcIErer8cNjes9BmURniDiYCEnPbqmD50f/ucJtJOomjF
 dOVrxKOTm5TQYOgMUEwPqSY/3mViilXEVQbnT6sA=
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/95984] [11 Regression] Internal compiler
 error: Error reporting routines re-entered. since r11-1697-g75ff24e1920ea6b1
Date: Mon, 29 Jun 2020 20:46:04 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 11.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor 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: cf_reconfirmed_on cc bug_status everconfirmed
Message-ID: <bug-95984-4-uCyalAfHEw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-95984-4@http.gcc.gnu.org/bugzilla/>
References: <bug-95984-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: Mon, 29 Jun 2020 20:46:04 -0000

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

Martin Sebor <msebor at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|                            |2020-06-29
                 CC|                            |jason at gcc dot gnu.org,
                   |                            |mpolacek at gcc dot gnu.org
             Status|UNCONFIRMED                 |NEW
     Ever confirmed|0                           |1

--- Comment #1 from Martin Sebor <msebor at gcc dot gnu.org> ---
If I'm reading the dump right the front end constructs a lambda object and
calls its member operator() with a null this pointer:

;; Function static decltype (((const callback<main()::<lambda(int)>
>::<lambda(auto:1 ...)>*)0)->operator()<auto:1
...>(static_cast<auto:1&&>(callback::._anon_2::_FUN::<unnamed>) ...))
callback<main()::<lambda(int)> >::<lambda(auto:1 ...)>::_FUN(auto:1 ...) [w=
ith
auto:1 =3D {int}; decltype (((const callback<main()::<lambda(int)>
>::<lambda(auto:1 ...)>*)0)->operator()<auto:1
...>(static_cast<auto:1&&>(callback::._anon_2::_FUN::<unnamed>) ...)) =3D v=
oid]
(null)
;; enabled by -tree-original


<<cleanup_point <<< Unknown tree: expr_stmt
  callback<main()::<lambda(int)> >::<lambda(auto:1 ...)>::operator()<int> (=
0B,
D.2439) >>>>>;
return;

So it seems like the warning code is doing what it's supposed to.

The ICE is triggered by the C++ front end printing the instantiation context
(print_instantiation_full_context), the pretty printer formatting the templ=
ate
specialization, calling into the C++ front end to perform type substitution,
and the FE ending up calling check_nonnull_arg() on the call, which ends up
triggering the warning and re-entering the diagnostic machinery.  There is
nothing out of the ordinary the warning does to do this so it must be a lat=
ent
problem in the C++ front end that the warning exposed.  I expect Jason or M=
arek
have seen and deal with something like this before.=