public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88309] [11/12/13/14 Regression] ICE: Floating point exception (in is_miss_rate_acceptable), target assigning alignent of 4 bits(!) to vector
Date: Tue, 02 Apr 2024 14:36:43 +0000 [thread overview]
Message-ID: <bug-88309-4-PGfJn1lScc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-88309-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88309
--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Kewen Lin from comment #4)
> (In reply to Andrew Pinski from comment #3)
> > Found it:
> > /* In GIMPLE the type of the MEM_REF specifies the alignment. The
> > required alignment (power) is 4 bytes regardless of data type. */
> > tree align_ltype = build_aligned_type (lhs_type, 4);
> >
> > That should be 4*8 instead of just 4.
> >
> > There are 2 build_aligned_type in rs6000-builtins.cc which uses the wrong
> > alignment; thinking it was the alignment argument was bytes rather than bits.
> >
> > Introduced by r9-2375-g3f7a77cd20d07c which means this is a regression.
>
> Hi Andrew, thanks for digging into this! William has not worked on GCC
> project any more, will you make a patch for this?
I don't have time to test it really.
next prev parent reply other threads:[~2024-04-02 14:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-88309-4@http.gcc.gnu.org/bugzilla/>
2024-03-25 18:23 ` [Bug target/88309] " pinskia at gcc dot gnu.org
2024-03-31 8:26 ` [Bug target/88309] [11/12/13/14 Regression] " pinskia at gcc dot gnu.org
2024-04-02 8:36 ` linkw at gcc dot gnu.org
2024-04-02 14:36 ` pinskia at gcc dot gnu.org [this message]
2024-04-03 1:47 ` linkw at gcc dot gnu.org
2024-04-09 2:03 ` cvs-commit at gcc dot gnu.org
2024-04-25 2:35 ` cvs-commit at gcc dot gnu.org
2024-04-25 2:35 ` cvs-commit at gcc dot gnu.org
2024-04-25 5:09 ` cvs-commit at gcc dot gnu.org
2024-04-25 5:12 ` 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-88309-4-PGfJn1lScc@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).