Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: Tianjia Zhang <tianjia.zhang@linux.alibaba.com>
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
	Nick Desaulniers <ndesaulniers@google.com>,
	Adrian Schmutzler <freifunk@adrianschmutzler.de>,
	linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MIPS: Octeon: Fix build errors using clang
Date: Thu, 16 Dec 2021 09:11:33 -0700	[thread overview]
Message-ID: <YbtlNT7WUi3b8Dqh@archlinux-ax161> (raw)
In-Reply-To: <20211216095014.11918-1-tianjia.zhang@linux.alibaba.com>

On Thu, Dec 16, 2021 at 05:50:14PM +0800, Tianjia Zhang wrote:
> A large number of the following errors is reported when compiling
> with clang:
> 
>   cvmx-bootinfo.h:326:3: error: adding 'int' to a string does not append to the string [-Werror,-Wstring-plus-int]
>                   ENUM_BRD_TYPE_CASE(CVMX_BOARD_TYPE_NULL)
>                   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>   cvmx-bootinfo.h:321:20: note: expanded from macro 'ENUM_BRD_TYPE_CASE'
>           case x: return(#x + 16);        /* Skip CVMX_BOARD_TYPE_ */
>                          ~~~^~~~
>   cvmx-bootinfo.h:326:3: note: use array indexing to silence this warning
>   cvmx-bootinfo.h:321:20: note: expanded from macro 'ENUM_BRD_TYPE_CASE'
>           case x: return(#x + 16);        /* Skip CVMX_BOARD_TYPE_ */
>                           ^
> 
> Follow the prompts to use the address operator '&' to fix this error.
> 
> Signed-off-by: Tianjia Zhang <tianjia.zhang@linux.alibaba.com>

Reviewed-by: Nathan Chancellor <nathan@kernel.org>

> ---
>  arch/mips/include/asm/octeon/cvmx-bootinfo.h | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/arch/mips/include/asm/octeon/cvmx-bootinfo.h b/arch/mips/include/asm/octeon/cvmx-bootinfo.h
> index 0e6bf220db61..6c61e0a63924 100644
> --- a/arch/mips/include/asm/octeon/cvmx-bootinfo.h
> +++ b/arch/mips/include/asm/octeon/cvmx-bootinfo.h
> @@ -318,7 +318,7 @@ enum cvmx_chip_types_enum {
>  
>  /* Functions to return string based on type */
>  #define ENUM_BRD_TYPE_CASE(x) \
> -	case x: return(#x + 16);	/* Skip CVMX_BOARD_TYPE_ */
> +	case x: return (&#x[16]);	/* Skip CVMX_BOARD_TYPE_ */
>  static inline const char *cvmx_board_type_to_string(enum
>  						    cvmx_board_types_enum type)
>  {
> @@ -410,7 +410,7 @@ static inline const char *cvmx_board_type_to_string(enum
>  }
>  
>  #define ENUM_CHIP_TYPE_CASE(x) \
> -	case x: return(#x + 15);	/* Skip CVMX_CHIP_TYPE */
> +	case x: return (&#x[15]);	/* Skip CVMX_CHIP_TYPE */
>  static inline const char *cvmx_chip_type_to_string(enum
>  						   cvmx_chip_types_enum type)
>  {
> -- 
> 2.32.0
> 

  reply	other threads:[~2021-12-16 16:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-16  9:50 [PATCH] MIPS: Octeon: Fix build errors using clang Tianjia Zhang
2021-12-16 16:11 ` Nathan Chancellor [this message]
2021-12-17 23:58 ` Philippe Mathieu-Daudé
2021-12-21 13:57 ` Thomas Bogendoerfer

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=YbtlNT7WUi3b8Dqh@archlinux-ax161 \
    --to=nathan@kernel.org \
    --cc=freifunk@adrianschmutzler.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=tianjia.zhang@linux.alibaba.com \
    --cc=tsbogend@alpha.franken.de \
    /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