public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rdapp at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/112929] [14] RISC-V vector: Variable clobbered at runtime
Date: Mon, 11 Dec 2023 08:03:23 +0000	[thread overview]
Message-ID: <bug-112929-4-jhDDJfjole@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112929-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #13 from Robin Dapp <rdapp at gcc dot gnu.org> ---
I just built from the most recent commit and it still fails for me.
Could there be a difference in qemu?  I'm on qemu-riscv64 version 8.1.91 but
yours is even newer so that might not explain it.

You could step through until the last vsetvl before the printf and check the vl
after it (or the avl in a4).
As we overwrite the stack it might lead to different outcomes on different
environments.

  parent reply	other threads:[~2023-12-11  8:03 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-09  1:44 [Bug target/112929] New: " patrick at rivosinc dot com
2023-12-09  2:01 ` [Bug target/112929] " pinskia at gcc dot gnu.org
2023-12-09  2:49 ` patrick at rivosinc dot com
2023-12-09  3:03 ` patrick at rivosinc dot com
2023-12-09  3:34 ` pinskia at gcc dot gnu.org
2023-12-09  3:38 ` pinskia at gcc dot gnu.org
2023-12-09 13:33 ` rdapp at gcc dot gnu.org
2023-12-09 13:40 ` rdapp at gcc dot gnu.org
2023-12-09 14:04 ` juzhe.zhong at rivai dot ai
2023-12-09 14:06 ` rdapp at gcc dot gnu.org
2023-12-09 14:18 ` juzhe.zhong at rivai dot ai
2023-12-10 12:41 ` pan2.li at intel dot com
2023-12-11  2:27 ` pan2.li at intel dot com
2023-12-11  8:03 ` rdapp at gcc dot gnu.org [this message]
2023-12-11 17:35 ` patrick at rivosinc dot com
2023-12-11 19:16 ` rdapp at gcc dot gnu.org
2023-12-11 19:41 ` patrick at rivosinc dot com
2023-12-11 19:42 ` patrick at rivosinc dot com
2023-12-12  5:51 ` pan2.li at intel dot com
2023-12-12  8:52 ` pan2.li at intel dot com
2023-12-12  9:06 ` kito at gcc dot gnu.org
2023-12-13 12:01 ` cvs-commit at gcc dot gnu.org
2023-12-13 14:08 ` cvs-commit at gcc dot gnu.org
2023-12-13 16:23 ` patrick at rivosinc dot com

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-112929-4-jhDDJfjole@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).