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 tree-optimization/113178] [14 Regression] ice in find_uses_to_rename_use
Date: Sat, 30 Dec 2023 18:46:22 +0000 [thread overview]
Message-ID: <bug-113178-4-fIkDgB8Uca@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113178-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113178
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Keywords| |needs-bisection
Ever confirmed|0 |1
Last reconfirmed| |2023-12-30
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
More reduced testcase and converted into one is C code too:
```
struct PixelWeight {
int m_SrcStart;
int m_Weights[16];
};
char h;
void f(struct PixelWeight *pPixelWeights) {
int dest_g_m;
long tt;
for (int j = 0; j < 16; j++) {
int *p = 0;
if (j < pPixelWeights->m_SrcStart)
p = tt ? &pPixelWeights->m_Weights[0] : 0;
int pWeight = *p;
dest_g_m += pWeight;
}
h = dest_g_m;
}
```
next prev parent reply other threads:[~2023-12-30 18:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-30 10:15 [Bug c++/113178] New: " dcb314 at hotmail dot com
2023-12-30 18:36 ` [Bug tree-optimization/113178] [14 Regression] " pinskia at gcc dot gnu.org
2023-12-30 18:46 ` pinskia at gcc dot gnu.org [this message]
2023-12-30 19:38 ` dcb314 at hotmail dot com
2023-12-30 20:28 ` dcb314 at hotmail dot com
2023-12-30 20:56 ` dcb314 at hotmail dot com
2024-01-02 10:09 ` tnfchris at gcc dot gnu.org
2024-01-10 13:27 ` rguenth at gcc dot gnu.org
2024-01-10 18:02 ` jamborm at gcc dot gnu.org
2024-01-12 15:32 ` cvs-commit at gcc dot gnu.org
2024-01-12 15:32 ` cvs-commit at gcc dot gnu.org
2024-01-12 15:36 ` tnfchris 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-113178-4-fIkDgB8Uca@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).