From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 7C38C3856DC0; Fri, 21 Oct 2022 13:04:00 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 7C38C3856DC0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1666357440; bh=qA6xWA3SaJCSosupvmeJmJyyWHtkfV2Tmbx5G25/3wU=; h=From:To:Subject:Date:In-Reply-To:References:From; b=Q3FfGMnqBmo+tLrAsWgyHXoHspN4zRgBhInZkhNcLCi9uw61yKdBxlFWODlih+mJC 6Z8YCssbv+B1YfWYT7dxMLJlNrNVJ9fAnuDq0Bdpjjfl3vGkoxHbWbIJSG++r4dJS1 FF5Ygcl3xKOhteA9zgjAa33hFPrwEHYiSZxZRy3E= From: "linkw at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/107338] new test case gcc.dg/vect/vect-bitfield-read-7.c in r13-3413-ge10ca9544632db fails Date: Fri, 21 Oct 2022 13:04:00 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: testsuite X-Bugzilla-Version: 13.0 X-Bugzilla-Keywords: testsuite-fail X-Bugzilla-Severity: normal X-Bugzilla-Who: linkw at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: linkw at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status assigned_to 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=3D107338 Kewen Lin changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED Assignee|unassigned at gcc dot gnu.org |linkw at gcc dot gn= u.org --- Comment #4 from Kewen Lin --- (In reply to avieira from comment #3) > Hi Kewen, >=20 > I believe you are right. I was waiting for a powerpc machine in the board > farm, but I suspect I can reproduce this with an aarch64 BE target and I > should be able to confirm. >=20 > But your reasoning seems valid to me. Because of the widening the shift_n > becomes 32-shift_n-mask_width, but the start of the bitfield didn't move = by > widening the container, so it is still 16 - shift_n - mask_width bits away > from the start of the container. >=20 > Moving the calculation before the widening seems like the neatest solution > to me, there's no point in keeping the old type around I think. >=20 > Do you want to produce a patch for this, seeing you solved it? Hi Andre, Thanks for your reply! Sure, I'll make a formal patch and do further bootstrap/regtest on x86_64-redhat-linux, aarch64-linux-gnu and powerpc64{,le}-linux-gnu, and post it once the testing go well.=