public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vineetg at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/112447] risc-v regression: FAIL: gcc.c-torture/execute/memset-3.c -O3
Date: Wed, 08 Nov 2023 23:00:43 +0000 [thread overview]
Message-ID: <bug-112447-4-EP3EFLsI3t@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112447-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112447
Vineet Gupta <vineetg at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Last reconfirmed| |2023-11-08
Status|UNCONFIRMED |ASSIGNED
--- Comment #9 from Vineet Gupta <vineetg at gcc dot gnu.org> ---
(In reply to JuzheZhong from comment #7)
> Oh. I missed it:
>
> vmv.v.x v2,s0
> vse8.v v2,0(a5)
>
> Leave it to me today. It should be simple fix.
>
> Thanks for report it.
Can I request you to let me continue to debug and fix it. I want to familiarize
myself with the vsetv pass and this seems like a good opportunity to do so
considering you think the fix is not hard.
next prev parent reply other threads:[~2023-11-08 23:00 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-08 20:11 [Bug target/112447] New: " vineetg at gcc dot gnu.org
2023-11-08 22:05 ` [Bug target/112447] " juzhe.zhong at rivai dot ai
2023-11-08 22:33 ` vineetg at gcc dot gnu.org
2023-11-08 22:34 ` vineetg at gcc dot gnu.org
2023-11-08 22:35 ` vineetg at gcc dot gnu.org
2023-11-08 22:40 ` juzhe.zhong at rivai dot ai
2023-11-08 22:46 ` vineetg at gcc dot gnu.org
2023-11-08 22:49 ` juzhe.zhong at rivai dot ai
2023-11-08 22:52 ` juzhe.zhong at rivai dot ai
2023-11-08 23:00 ` vineetg at gcc dot gnu.org [this message]
2023-11-08 23:01 ` juzhe.zhong at rivai dot ai
2023-11-14 20:02 ` vineetg at gcc dot gnu.org
2023-11-14 22:29 ` juzhe.zhong at rivai dot ai
2023-11-14 23:18 ` vineetg at gcc dot gnu.org
2023-11-14 23:23 ` juzhe.zhong at rivai dot ai
2023-11-14 23:34 ` vineetg at gcc dot gnu.org
2023-11-15 1:04 ` juzhe.zhong at rivai dot ai
2023-11-15 1:07 ` juzhe.zhong at rivai dot ai
2023-11-15 2:03 ` juzhe.zhong at rivai dot ai
2023-11-15 2:49 ` juzhe.zhong at rivai dot ai
2023-11-15 2:57 ` juzhe.zhong at rivai dot ai
2023-11-15 17:35 ` cvs-commit at gcc dot gnu.org
2023-11-15 17:53 ` vineetg 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-112447-4-EP3EFLsI3t@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).