public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "slyfox at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/111048] [14 Regression] Wrong AVX2 code on highway-1.0.6 on -O2 and above
Date: Thu, 17 Aug 2023 12:35:23 +0000 [thread overview]
Message-ID: <bug-111048-4-wgiXk515Af@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111048-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111048
Sergei Trofimovich <slyfox at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |richard.sandiford at arm dot com
--- Comment #1 from Sergei Trofimovich <slyfox at gcc dot gnu.org> ---
`git bisect` points at r14-3243-ga7dba4a1c05a76:
commit a7dba4a1c05a76026d88dcccc0b519cf83bff9a2
Date: Wed Aug 16 16:51:44 2023 +0530
Extend fold_vec_perm to handle VLA vector_cst.
next prev parent reply other threads:[~2023-08-17 12:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 11:40 [Bug target/111048] New: " slyfox at gcc dot gnu.org
2023-08-17 12:35 ` slyfox at gcc dot gnu.org [this message]
2023-08-17 18:32 ` [Bug middle-end/111048] " pinskia at gcc dot gnu.org
2023-08-17 18:39 ` [Bug tree-optimization/111048] " pinskia at gcc dot gnu.org
2023-08-18 7:39 ` rguenth at gcc dot gnu.org
2023-08-18 8:24 ` cvs-commit at gcc dot gnu.org
2023-08-18 8:25 ` rguenth at gcc dot gnu.org
2023-08-18 9:08 ` prathamesh3492 at gcc dot gnu.org
2023-08-18 9:35 ` rsandifo at gcc dot gnu.org
2023-08-18 14:27 ` [Bug tree-optimization/111048] [14 Regression] Wrong AVX2 code on highway-1.0.6 on -O2 and above since r14-3243-ga7dba4a1c05a76 prathamesh3492 at gcc dot gnu.org
2023-08-21 9:57 ` cvs-commit at gcc dot gnu.org
2023-08-21 11:04 ` prathamesh3492 at gcc dot gnu.org
2023-08-21 17:49 ` slyfox 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-111048-4-wgiXk515Af@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).