public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fanghuaqi at vip dot qq.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/112537] Is there a way to disable cpymem pass for rvv
Date: Wed, 15 Nov 2023 05:14:23 +0000	[thread overview]
Message-ID: <bug-112537-4-JtVBkaYLC8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112537-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Huaqi <fanghuaqi at vip dot qq.com> ---
(In reply to JuzheZhong from comment #4)
> You mean you want to disable it when disabling auto-vectorization ?

Yes, I think this could be better, so we can control whether vector instruction
should be generated, and if auto generated rvv instruction is not good, we can
enable it via gcc pragma control for selected code block.

Thanks

  parent reply	other threads:[~2023-11-15  5:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-15  3:07 [Bug c/112537] New: " fanghuaqi at vip dot qq.com
2023-11-15  3:13 ` [Bug target/112537] " pinskia at gcc dot gnu.org
2023-11-15  4:45 ` juzhe.zhong at rivai dot ai
2023-11-15  5:03 ` fanghuaqi at vip dot qq.com
2023-11-15  5:05 ` juzhe.zhong at rivai dot ai
2023-11-15  5:14 ` fanghuaqi at vip dot qq.com [this message]
2023-11-15  5:17 ` juzhe.zhong at rivai dot ai
2023-11-15  5:53 ` pinskia at gcc dot gnu.org
2023-11-15  6:42 ` kito at gcc dot gnu.org
2023-11-15  6:44 ` juzhe.zhong at rivai dot ai
2023-11-15  7:12 ` juzhe.zhong at rivai dot ai
2023-11-15  7:34 ` kito at gcc dot gnu.org
2023-11-17 13:23 ` amylaar at gcc dot gnu.org
2023-11-17 13:27 ` amylaar at gcc dot gnu.org
2023-11-20  2:50 ` 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-112537-4-JtVBkaYLC8@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).