public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/109502] [11 Regression] wrong code with -O -ftree-vectorize -fvect-cost-model=unlimited on aarch64 Date: Mon, 17 Apr 2023 09:21:25 +0000 [thread overview] Message-ID: <bug-109502-4-6aIYV2UZI0@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109502-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109502 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|12.3 |11.4 Known to work| |12.2.1 Summary|[12 Regression] wrong code |[11 Regression] wrong code |with -O -ftree-vectorize |with -O -ftree-vectorize |-fvect-cost-model=unlimited |-fvect-cost-model=unlimited |on aarch64 |on aarch64 Known to fail|12.2.1 |12.2.0 --- Comment #8 from Richard Biener <rguenth at gcc dot gnu.org> --- Also picks to 11.
next prev parent reply other threads:[~2023-04-17 9:21 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-13 16:05 [Bug target/109502] New: [12/13 " zsojka at seznam dot cz 2023-04-14 1:56 ` [Bug target/109502] " pinskia at gcc dot gnu.org 2023-04-14 2:03 ` [Bug tree-optimization/109502] " pinskia at gcc dot gnu.org 2023-04-14 2:04 ` pinskia at gcc dot gnu.org 2023-04-14 7:28 ` rguenth at gcc dot gnu.org 2023-04-14 7:53 ` rguenth at gcc dot gnu.org 2023-04-14 9:46 ` cvs-commit at gcc dot gnu.org 2023-04-14 9:46 ` [Bug tree-optimization/109502] [12 " rguenth at gcc dot gnu.org 2023-04-17 9:15 ` cvs-commit at gcc dot gnu.org 2023-04-17 9:21 ` rguenth at gcc dot gnu.org [this message] 2023-05-02 12:03 ` [Bug tree-optimization/109502] [11 " cvs-commit at gcc dot gnu.org 2023-05-02 12:06 ` 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-109502-4-6aIYV2UZI0@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).