public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/113896] [12 Regression] Assigning array elements in the wrong order after floating point optimization since r12-8841 Date: Tue, 13 Feb 2024 12:42:36 +0000 [thread overview] Message-ID: <bug-113896-4-Z1ANGcyB49@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113896-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113896 --- Comment #5 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>: https://gcc.gnu.org/g:4a1cd5560b9b545eb848eb1d1e06d345fb606f76 commit r14-8957-g4a1cd5560b9b545eb848eb1d1e06d345fb606f76 Author: Richard Biener <rguenther@suse.de> Date: Tue Feb 13 13:39:29 2024 +0100 tree-optimization/113896 - testcase for fixed PR The SLP permute optimization rewrite fixed this. PR tree-optimization/113896 * g++.dg/torture/pr113896.C: New testcase.
next prev parent reply other threads:[~2024-02-13 12:42 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-13 0:00 [Bug c++/113896] New: Assigning array elements in the wrong order after floating point optimization noobie-iv at mail dot ru 2024-02-13 0:05 ` [Bug tree-optimization/113896] [12 Regression] " pinskia at gcc dot gnu.org 2024-02-13 0:16 ` [Bug tree-optimization/113896] [12 Regression] Assigning array elements in the wrong order after floating point optimization since r12-8841 pinskia at gcc dot gnu.org 2024-02-13 8:42 ` rguenth at gcc dot gnu.org 2024-02-13 8:43 ` rguenth at gcc dot gnu.org 2024-02-13 12:36 ` rguenth at gcc dot gnu.org 2024-02-13 12:42 ` cvs-commit at gcc dot gnu.org [this message] 2024-02-13 12:48 ` cvs-commit at gcc dot gnu.org 2024-02-14 11:43 ` cvs-commit at gcc dot gnu.org 2024-02-14 11:43 ` rguenth at gcc dot gnu.org 2024-02-15 3:16 ` noobie-iv at mail dot ru
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-113896-4-Z1ANGcyB49@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).