From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id B8FC33853D57; Fri, 18 Nov 2022 07:07:35 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B8FC33853D57 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1668755255; bh=ZJRHGwFQaXp+lZ2iR1VRU+3qKaczi3Bmdv/gSiP8TRM=; h=From:To:Subject:Date:In-Reply-To:References:From; b=Ci0dxX2bsjGk/g/usi798/lY/bHq4xJhB/bZi+Sw+RfIqAEkQr/IgibuJua+7KYGi budWGkm9Mg/fc1aH3UwmXUtbEivB1SSrZXjWZaKpGfkyP4c3rT9OxSzhWRIgtMurJ5 Wxsherz+krC9EA0H1YzMFws7DXrL+zcTEeOgkMvs= From: "wwwhhhyyy333 at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/107692] [13 regression] r13-3950-g071e428c24ee8c breaks many test cases Date: Fri, 18 Nov 2022 07:07:35 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 13.0 X-Bugzilla-Keywords: testsuite-fail X-Bugzilla-Severity: normal X-Bugzilla-Who: wwwhhhyyy333 at gmail dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 13.0 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=3D107692 --- Comment #6 from Hongyu Wang --- (In reply to Jiu Fu Guo from comment #4) > (In reply to Hongyu Wang from comment #2) > > Created attachment 53897 [details] > > A patch > >=20 > > Sorry for introducing these fails. Here is the patch. > >=20 > > I've tested the patch with cross-compler and all the fails disappeared,= but > > I don't have a powerpc to do full bootstrap & regtest (I'm still applyi= ng > > for gcc farm account). > >=20 > > I'll send out the patch after I can access gcc farm for a power machine= , or > > hopefully someone can help testing the patch. > >=20 > > I suppose s390 has similar issue and I will update that accordingly. > Hi, >=20 > One small comment, for code "if (!(flag_unroll_loops || > flag_unroll_all_loops))" > we may need to add one more condition "|| loop->unroll", like what does in > r13-3950 for i386.cc. Otherwise, unroll pragma may be affected. Yes, I've already posted the patch at https://gcc.gnu.org/pipermail/gcc-patches/2022-November/606478.html=