public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "manolis.tsamis at vrull dot eu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/113089] [14 Regression][aarch64] ICE in process_uses_of_deleted_def, at rtl-ssa/changes.cc:252 since r14-6605-gc0911c6b357ba9 Date: Wed, 20 Dec 2023 10:21:13 +0000 [thread overview] Message-ID: <bug-113089-4-34sefdGH7d@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113089-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113089 Manolis Tsamis <manolis.tsamis at vrull dot eu> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |manolis.tsamis at vrull dot eu --- Comment #2 from Manolis Tsamis <manolis.tsamis at vrull dot eu> --- The following testcase, reduced from x264 intrapred_chroma_plane: typedef unsigned short uint16; void intrapred_chroma_plane(uint16 ***mb_preds, int* max_imgpel_values, int crx, int cry, int px) { for (int uv = 0; uv < 2; uv++) { uint16 **mb_pred = mb_preds[uv + 1]; uint16 **predU2 = &mb_pred[px - 2]; uint16 *upPred = &mb_pred[px][px]; int max_imgpel_value = max_imgpel_values[uv]; int ih = upPred[crx - 1]; for (int i = 0; i < crx*3; ++i) ih += upPred[crx*3]; int iv = (mb_pred[cry - 1][px+1]); for (int i = 0; i < cry - 1; ++i) { iv += (i + 1) * (*(mb_preds[uv][0]) - *(*predU2--)); } for (int j = 0; j < cry; ++j) for (int i = 0; i < crx; ++i) mb_pred[j][i] = (uint16) (max_imgpel_value * ((i * ih + iv))); } } reproduces the same ICE issue when compiled with: gcc -g -O2 -funroll-loops -fno-strict-aliasing intra_chroma_pred.c
next prev parent reply other threads:[~2023-12-20 10:21 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-20 3:12 [Bug target/113089] New: " hliu at amperecomputing dot com 2023-12-20 3:14 ` [Bug target/113089] " pinskia at gcc dot gnu.org 2023-12-20 8:02 ` rguenth at gcc dot gnu.org 2023-12-20 10:21 ` manolis.tsamis at vrull dot eu [this message] 2023-12-20 10:22 ` manolis.tsamis at vrull dot eu 2023-12-20 10:30 ` acoplan at gcc dot gnu.org 2023-12-20 10:44 ` acoplan at gcc dot gnu.org 2023-12-20 10:48 ` manolis.tsamis at vrull dot eu 2023-12-20 10:59 ` acoplan at gcc dot gnu.org 2023-12-20 11:03 ` manolis.tsamis at vrull dot eu 2023-12-20 11:05 ` acoplan at gcc dot gnu.org 2023-12-20 12:08 ` acoplan at gcc dot gnu.org 2024-01-08 12:51 ` jakub at gcc dot gnu.org 2024-01-18 15:08 ` acoplan at gcc dot gnu.org 2024-01-19 9:18 ` acoplan at gcc dot gnu.org 2024-01-23 16:50 ` cvs-commit at gcc dot gnu.org 2024-01-23 16:51 ` cvs-commit at gcc dot gnu.org 2024-01-23 16:51 ` cvs-commit at gcc dot gnu.org 2024-01-23 16:55 ` acoplan 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-113089-4-34sefdGH7d@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: linkBe 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).