From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 050A13858D20; Fri, 1 Sep 2023 02:09:32 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 050A13858D20 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1693534172; bh=zrKNwFLYl9kRvR0dOx+lBAA71jPDGK4TKU9eeBVLckY=; h=From:To:Subject:Date:In-Reply-To:References:From; b=BHUvia0HhCbrs3/V96WBxHseuvA251eBJ3GZn2jrLJw3ojlLBnptVdhCGE18gJiFp mV/ryW/uzlKAlAtJFEKe1N5/tUBc5OaRc0jzOSd3pz/dbSS70rH4xsWkg4NMLoAntb OGiunC+sTIYiLK/1X+7Iq1PkfKXIzFoexFLN/HNo= From: "hp at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug other/111264] [14 regression] gcc.dg/plugin/analyzer_cpython_plugin.c breaks after r14-3580-g597b9ec69bca8a Date: Fri, 01 Sep 2023 02:09:30 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: other X-Bugzilla-Version: 14.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: hp at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: efric at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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=3D111264 Hans-Peter Nilsson changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hp at gcc dot gnu.org --- Comment #1 from Hans-Peter Nilsson --- Also seen for cris-elf and m68k-linux (https://gcc.gnu.org/pipermail/gcc-testresults/2023-August/794806.html). Some experimentation says that this is a mismatch between the default C++ version for the host/installed gcc (for me, C++11, I think) and the target (C++17, right?). If you add "-std=3Dc++17" to the invocation line in gcc.l= og, compilation succeeds. Or, change the form of the newly introduced declarat= ions from auto foobar =3D foo(); to foo foobar; Not sure why the former is used, it seems negate the benefits of auto and j= ust be more typing. Beware: since I know Very Little C++ of the last decades, I could be completely wrong.=