public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "kristerw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/110495] New: fre introduces signed wrap for vector Date: Fri, 30 Jun 2023 09:06:41 +0000 [thread overview] Message-ID: <bug-110495-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110495 Bug ID: 110495 Summary: fre introduces signed wrap for vector Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: kristerw at gcc dot gnu.org Target Milestone: --- The following function (from gcc.dg/tree-ssa/addadd-2.c) typedef int S __attribute__((vector_size(64))); void j(S*x){ *x += __INT_MAX__; *x += __INT_MAX__; } is optimized by fre1 to void j (S * x) { vector(16) int _1; vector(16) int _2; vector(16) int _4; <bb 2> : _1 = *x_6(D); _2 = _1 + { 2147483647, 2147483647, 2147483647, 2147483647, 2147483647, 2147483647, 2147483647, 2147483647, 2147483647, 2147483647, 2147483647, 2147483647, 2147483647, 2147483647, 2147483647, 2147483647 }; *x_6(D) = _2; _4 = _1 + { -2(OVF), -2(OVF), -2(OVF), -2(OVF), -2(OVF), -2(OVF), -2(OVF), -2(OVF), -2(OVF), -2(OVF), -2(OVF), -2(OVF), -2(OVF), -2(OVF), -2(OVF), -2(OVF) }; *x_6(D) = _4; return; } which has signed wrap for the cases where the original did not wrap.
next reply other threads:[~2023-06-30 9:06 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-30 9:06 kristerw at gcc dot gnu.org [this message] 2023-06-30 9:33 ` [Bug middle-end/110495] " rguenth at gcc dot gnu.org 2023-07-03 8:09 ` rsandifo at gcc dot gnu.org 2023-07-03 8:40 ` rguenth at gcc dot gnu.org 2023-07-03 8:43 ` rguenth at gcc dot gnu.org 2023-07-04 7:08 ` cvs-commit at gcc dot gnu.org 2023-07-04 7:09 ` rguenth 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-110495-4@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).