public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "crazylht at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/106022] [12/13 Regression] Enable vectorizer generates extra load
Date: Thu, 30 Jun 2022 03:48:53 +0000	[thread overview]
Message-ID: <bug-106022-4-TM7gs5IGy2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106022-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106022

--- Comment #17 from Hongtao.liu <crazylht at gmail dot com> ---
(In reply to H.J. Lu from comment #16)
> Created attachment 53227 [details]
> The v4 patch
> 
> Here is a different approach by supporting 2/4/8 byte constant vector stores.

It LGTM.

  parent reply	other threads:[~2022-06-30  3:48 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-17 21:59 [Bug target/106022] New: " hjl.tools at gmail dot com
2022-06-17 23:18 ` [Bug target/106022] " hjl.tools at gmail dot com
2022-06-20  2:07 ` crazylht at gmail dot com
2022-06-20 11:23 ` rguenth at gcc dot gnu.org
2022-06-20 11:24 ` rguenth at gcc dot gnu.org
2022-06-20 12:42 ` crazylht at gmail dot com
2022-06-20 14:07 ` hjl.tools at gmail dot com
2022-06-20 16:35 ` hjl.tools at gmail dot com
2022-06-21  6:41 ` rguenth at gcc dot gnu.org
2022-06-21 14:39 ` hjl.tools at gmail dot com
2022-06-21 22:23 ` hjl.tools at gmail dot com
2022-06-23  6:19 ` rguenth at gcc dot gnu.org
2022-06-24 21:22 ` hjl.tools at gmail dot com
2022-06-27  9:00 ` rguenther at suse dot de
2022-06-27 13:33 ` hjl.tools at gmail dot com
2022-06-28  6:44 ` rguenther at suse dot de
2022-06-29 21:53 ` hjl.tools at gmail dot com
2022-06-30  3:48 ` crazylht at gmail dot com [this message]
2022-07-03 17:30 ` cvs-commit at gcc dot gnu.org
2022-07-25 15:57 ` [Bug target/106022] [12 " rguenth at gcc dot gnu.org
2022-07-27  7:26 ` rguenth at gcc dot gnu.org
2023-01-18  9:57 ` jakub at gcc dot gnu.org
2023-05-08 12:24 ` 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-106022-4-TM7gs5IGy2@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).