public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Kito Cheng <kito.cheng@gmail.com>
To: Yeting Kuo <fakepaper56@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: RISC-V: fix a typo in riscv.h
Date: Mon, 14 Sep 2020 15:19:28 +0800	[thread overview]
Message-ID: <CA+yXCZB4BBO8f1Na_zaDPee03r3321ZOr70kk2PyFj6ZcP8GoA@mail.gmail.com> (raw)
In-Reply-To: <CAGhUdNiwPvWG_kBWMZoq5XUGUhiqLVnyzQtshxQAA2J9Ff1ZLw@mail.gmail.com>

Hi Yeting:

Could you provide a test case for that?

On Mon, Sep 14, 2020 at 3:15 PM Yeting Kuo via Gcc-patches
<gcc-patches@gcc.gnu.org> wrote:
>
> Hi all,
>
> The patch fixes a typo that would make some errors in fast-unaligned-access
> targets.
>
>     RISC-V: fix a typo in riscv.h
>
>     2020-09-14 Yeting Kuo <fakepaper56@gmail.com>
>
>     gcc/
>             * config/riscv/riscv.h
>
> diff --git a/gcc/config/riscv/riscv.h b/gcc/config/riscv/riscv.h
> index 9f67d82e74e..b7b4a1c88a5 100644
> --- a/gcc/config/riscv/riscv.h
> +++ b/gcc/config/riscv/riscv.h
> @@ -941,7 +941,7 @@ extern unsigned riscv_stack_boundary;
>
>  /* This is the maximum value that can be represented in a compressed
> load/store
>     offset (an unsigned 5-bit value scaled by 4).  */
> -#define CSW_MAX_OFFSET ((4LL << C_S_BITS) - 1) & ~3
> +#define CSW_MAX_OFFSET (((4LL << C_S_BITS) - 1) & ~3)
>
>  /* Called from RISCV_REORG, this is defined in riscv-sr.c.  */
>
> Best Regard,
> Yeting

  reply	other threads:[~2020-09-14  7:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-14  7:15 Yeting Kuo
2020-09-14  7:19 ` Kito Cheng [this message]
2020-09-14 11:06   ` Yeting Kuo
2020-09-17 21:30     ` 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=CA+yXCZB4BBO8f1Na_zaDPee03r3321ZOr70kk2PyFj6ZcP8GoA@mail.gmail.com \
    --to=kito.cheng@gmail.com \
    --cc=fakepaper56@gmail.com \
    --cc=gcc-patches@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).