From: Jeff Law <jeffreyalaw@gmail.com>
To: Patrick O'Neill <patrick@rivosinc.com>, gcc-patches@gcc.gnu.org
Cc: juzhe.zhong@rivai.ai, kito.cheng@gmail.com, rdapp.gcc@gmail.com,
gnu-toolchain@rivosinc.com
Subject: Re: [PATCH] RISC-V: Unescape chars in pr111566.f90 test
Date: Tue, 3 Oct 2023 15:55:10 -0600 [thread overview]
Message-ID: <7e5688b4-8e6f-44ca-bb68-87779748e063@gmail.com> (raw)
In-Reply-To: <20231003201945.907116-1-patrick@rivosinc.com>
On 10/3/23 14:19, Patrick O'Neill wrote:
> Some characters are escaped which causes the testcase to fail. This
> patch restores the original characters.
>
> Tested for regressions using multilib rv32gcv-ilp32d, rv64gcv-lp64d.
>
> gcc/testsuite/ChangeLog:
>
> * gcc.target/riscv/rvv/fortran/pr111566.f90: Restore escaped
> characters.
LOL. Yea, this is OK.
jeff
next prev parent reply other threads:[~2023-10-03 21:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 20:19 Patrick O'Neill
2023-10-03 21:55 ` Jeff Law [this message]
2023-10-03 22:04 ` [Committed] " Patrick O'Neill
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=7e5688b4-8e6f-44ca-bb68-87779748e063@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gnu-toolchain@rivosinc.com \
--cc=juzhe.zhong@rivai.ai \
--cc=kito.cheng@gmail.com \
--cc=patrick@rivosinc.com \
--cc=rdapp.gcc@gmail.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).