From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 94DCE3858CD1; Wed, 6 Dec 2023 10:43:21 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 94DCE3858CD1 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1701859401; bh=D/N8Iopsw3IQXCFUJ3FyOA5RmfgVz3RU0D9qhlYM5bk=; h=From:To:Subject:Date:In-Reply-To:References:From; b=SrY7KFIEUzdzXYZXVq000ExMluNq0SXEBdD8cRQitTsJrRnYNVd+SqwbxXSb1bm4e 5Lgx/4nb+A2iHxjJTU02nOupTbT7mCnAuuQWnm6PlSin1cambtMr6Jd/XeeU0OxPrx sSe/zjLMx58o73nIh8Ik2kNFc8gOuswTSSOodBnE= From: "rguenther at suse dot de" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/105562] [12 Regression] std::function::_M_invoker may be used uninitialized in std::regex move with -fno-strict-aliasing Date: Wed, 06 Dec 2023 10:43:21 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Version: 12.1.0 X-Bugzilla-Keywords: diagnostic, missed-optimization X-Bugzilla-Severity: normal X-Bugzilla-Who: rguenther at suse dot de X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org X-Bugzilla-Target-Milestone: 12.2 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=3D105562 --- Comment #26 from rguenther at suse dot de --- On Wed, 6 Dec 2023, romain.geissler at amadeus dot com wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D105562 >=20 > --- Comment #25 from Romain Geissler = --- > So it means we should rather go for "silencing" workaround from comment #= 19 ? No, I think people shouldn't care for warnings with -fsanitize=3D... (or not use -Wall).=