From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 2987B3858D35; Mon, 6 Jul 2020 21:42:39 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 2987B3858D35 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1594071759; bh=NnQxzmna8XFShr0um7yxW9z3UgJXfKA9NubeyZL83pI=; h=From:To:Subject:Date:In-Reply-To:References:From; b=ukQcUT20gvbsXxX3DTw57JvxXTHfL8OkPdLiiJTgioTxJMm7b6YDEwJpXJoZGq4z/ fBJpH5ev9FY60EVQMw5bmxDtkdYxvkEB7uSXDSo5GIJ7Oe/BKpX+yqaYxRaJ6SF2MF ZPmjm7QNE2LdI8cOdGBqJFenBYSq/3K8sRPHkOEg= From: "babokin at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/95396] [8/9/10/11 Regression] GCC produces incorrect code with -O3 for loops since r8-6511-g3ae129323d150621 Date: Mon, 06 Jul 2020 21:42:39 +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: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: babokin at gmail dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 8.5 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 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Jul 2020 21:42:39 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D95396 --- Comment #4 from Dmitry Babokin --- Richard Sandiford, could you please have a look as author of the commit, wh= ich brought the regression? We have a bunch of other fails, which might be or might be not the same as = this one. We'd like to avoid spamming developers with duplicates, so waiting for this bug to be fixed. Also, if there's a way how we can help investigating this bug, we would appreciate your guidance.=