public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: gcc-patches@gcc.gnu.org,
	Xianmiao Qu <cooper.qu@linux.alibaba.com>,
	Yunhai Shang <yunhai@linux.alibaba.com>
Subject: [ping] [PATCH] C-SKY: Fix unsigned comparison warning
Date: Sat, 17 Sep 2022 00:09:21 +0200	[thread overview]
Message-ID: <20220916220921.xpxt6ifmhmsi7hzf@lug-owl.de> (raw)
In-Reply-To: <20220912121923.fazqolix7neh77uz@lug-owl.de>

[-- Attachment #1: Type: text/plain, Size: 979 bytes --]

On Mon, 2022-09-12 14:19:23 +0200, Jan-Benedict Glaw <jbglaw@lug-owl.de> wrote:
> 2022-09-06  Jan-Benedict Glaw  <jbglaw@lug-owl.de>
> 
> gcc/ChangeLog:
> 	* config/csky/csky.h (FUNCTION_ARG_REGNO_P): Cast REGNO to (int)
> 	to prevent warning.
> 
> diff --git a/gcc/config/csky/csky.h b/gcc/config/csky/csky.h
> index 37410f0cda4..730d1b44ef1 100644
> --- a/gcc/config/csky/csky.h
> +++ b/gcc/config/csky/csky.h
> @@ -418,7 +418,7 @@ typedef struct
>     The int cast is to prevent a complaint about unsigned comparison to
>     zero, since CSKY_FIRST_PARM_REGNUM is zero.  */
>  #define FUNCTION_ARG_REGNO_P(REGNO)                          \
> -  (((REGNO) >= CSKY_FIRST_PARM_REGNUM                        \
> +  (((int)(REGNO) >= CSKY_FIRST_PARM_REGNUM                   \
>      && (REGNO) < (CSKY_NPARM_REGS + CSKY_FIRST_PARM_REGNUM)) \
>     || FUNCTION_VARG_REGNO_P(REGNO))
>  
> 
> Ok for HEAD?

Just wanted to give this a ping.

MfG, JBG

-- 

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2022-09-16 22:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-12 12:19 Jan-Benedict Glaw
2022-09-16 22:09 ` Jan-Benedict Glaw [this message]
2022-09-17  0:22 ` 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=20220916220921.xpxt6ifmhmsi7hzf@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --cc=cooper.qu@linux.alibaba.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=yunhai@linux.alibaba.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).