public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "linkw at gcc dot gnu.org" <gcc-bugzilla@gcc.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 [thread overview]
Message-ID: <bug-107338-4-ELjPNW6qzL@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107338-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107338
Kewen Lin <linkw at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |linkw at gcc dot gnu.org
--- Comment #4 from Kewen Lin <linkw at gcc dot gnu.org> ---
(In reply to avieira from comment #3)
> Hi Kewen,
>
> 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.
>
> 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.
>
> 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.
>
> 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.
next prev parent reply other threads:[~2022-10-21 13:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 21:58 [Bug other/107338] New: " seurer at gcc dot gnu.org
2022-10-20 22:05 ` [Bug other/107338] " pinskia at gcc dot gnu.org
2022-10-21 9:42 ` [Bug testsuite/107338] " linkw at gcc dot gnu.org
2022-10-21 10:59 ` avieira at gcc dot gnu.org
2022-10-21 13:04 ` linkw at gcc dot gnu.org [this message]
2022-10-25 5:20 ` cvs-commit at gcc dot gnu.org
2022-10-25 5:29 ` [Bug tree-optimization/107338] " linkw at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-107338-4-ELjPNW6qzL@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).