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 target/108429] [13 Regression] FAIL: gcc.target/i386/pr89618.c scan-tree-dump vect "LOOP VECTORIZED" Date: Mon, 06 Mar 2023 10:09:23 +0000 [thread overview] Message-ID: <bug-108429-4-ZH3QyzB89u@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108429-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108429 --- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jan Hubicka <hubicka@gcc.gnu.org>: https://gcc.gnu.org/g:b83acefb0409056b566133f66843ead6c04b8474 commit r13-6502-gb83acefb0409056b566133f66843ead6c04b8474 Author: Jan Hubicka <jh@suse.cz> Date: Mon Mar 6 11:08:26 2023 +0100 Enable scatter for generic 2023-03-06 Jan Hubicka <hubicka@ucw.cz> PR target/108429 * config/i386/x86-tune.def (X86_TUNE_USE_SCATTER_2PARTS): Enable for generic. (X86_TUNE_USE_SCATTER_4PARTS): Likewise. (X86_TUNE_USE_SCATTER): Likewise.
next prev parent reply other threads:[~2023-03-06 10:09 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-17 10:31 [Bug target/108429] New: " rguenth at gcc dot gnu.org 2023-01-17 10:33 ` [Bug target/108429] [13 Regression] " rguenth at gcc dot gnu.org 2023-01-17 10:36 ` rguenth at gcc dot gnu.org 2023-01-17 10:41 ` jakub at gcc dot gnu.org 2023-01-17 20:09 ` hubicka at gcc dot gnu.org 2023-02-21 13:04 ` rguenth at gcc dot gnu.org 2023-03-06 10:09 ` cvs-commit at gcc dot gnu.org [this message] 2023-03-06 10:10 ` hubicka at gcc dot gnu.org 2023-03-14 8:48 ` cvs-commit 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-108429-4-ZH3QyzB89u@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).