From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 2374B3858C54; Fri, 23 Sep 2022 18:11:57 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 2374B3858C54 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1663956717; bh=m646CwhuwjwNQ0rehiUYehvjf1zdXwVD7jal7CA1U8M=; h=From:To:Subject:Date:In-Reply-To:References:From; b=p12HgwKcKjzfJHH1MJdHMeePyv+KrMrabO3URUxG2duOX+FRb+BCMqkL/2mCMdevK vWK9x44tw0XjG82iA1pUI8s728CeHDMHzy3lcpOEQ18BSXlch7XLy+v8ODivmK2loR ihIy0jRngCbg6LmkxhyRwS80WCurTkVtvtjz7DbE= From: "andi at firstfloor dot org" To: gcc-bugs@gcc.gnu.org Subject: =?UTF-8?B?W0J1ZyBsdG8vOTk4MjhdIGlubGluaW5nIGZhaWxlZCBpbiBjYWxs?= =?UTF-8?B?IHRvIOKAmGFsd2F5c19pbmxpbmXigJkg4oCYbWVtY3B54oCZOiAtLXBhcmFt?= =?UTF-8?B?IG1heC1pbmxpbmUtaW5zbnMtYXV0byBsaW1pdCByZWFjaGVk?= Date: Fri, 23 Sep 2022 18:11:56 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: lto X-Bugzilla-Version: 11.0 X-Bugzilla-Keywords: diagnostic, missed-optimization X-Bugzilla-Severity: normal X-Bugzilla-Who: andi at firstfloor dot 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: 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=3D99828 --- Comment #15 from andi at firstfloor dot org --- > Provided I cannot reproduce on the current kernel, where exactly does thi= s come > from? Usually I had to do a longer loop of randconfig builds to find it. It only happens in some specific configs.=