From: Vineet Gupta <vineetg@rivosinc.com>
To: Jivan Hakobyan <jivanhakobyan9@gmail.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
Jeff Law <jlaw@ventanamicro.com>
Subject: Re: RISC-V: Fix stack_save_restore_1/2 test cases
Date: Thu, 24 Aug 2023 22:12:05 -0700 [thread overview]
Message-ID: <dcef29ba-60f6-09ee-a4ba-3a0a64679761@rivosinc.com> (raw)
In-Reply-To: <CAHso6sNkyz3m7xU8FtArMmCW_nJY4WCzePdQpn_SQEmvErbwmg@mail.gmail.com>
Hi Jivan,
On 8/24/23 08:45, Jivan Hakobyan via Gcc-patches wrote:
> This patch fixes failing stack_save_restore_1/2 test cases.
> After 6619b3d4c15c commit size of the frame was changed.
>
>
> gcc/testsuite/ChangeLog:
> * gcc.target/riscv/stack_save_restore_1.c: Update frame size
> * gcc.target/riscv/stack_save_restore_2.c: Likewise.
Do you mind sending your patches inline using git send-email or some such ?
Thx,
-Vineet
next prev parent reply other threads:[~2023-08-25 5:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-24 15:45 Jivan Hakobyan
2023-08-25 5:12 ` Vineet Gupta [this message]
2023-08-25 8:20 ` Jivan Hakobyan
2023-08-25 18:48 ` Jeff Law
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=dcef29ba-60f6-09ee-a4ba-3a0a64679761@rivosinc.com \
--to=vineetg@rivosinc.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jivanhakobyan9@gmail.com \
--cc=jlaw@ventanamicro.com \
/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).