All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: sparclinux@vger.kernel.org
Subject: Re: [PATCH] sparc: pass endianness info to sparse
Date: Thu, 02 Nov 2017 05:41:40 +0000	[thread overview]
Message-ID: <20171102054140.GA1454@ravnborg.org> (raw)
In-Reply-To: <20171031172210.9990-1-luc.vanoostenryck@gmail.com>

Hi Luc.

On Tue, Oct 31, 2017 at 06:22:10PM +0100, Luc Van Oostenryck wrote:
> sparc is big-endian only but sparse assumes the same endianness
> as the building machine.
> This is problematic for code which expect __BYTE_ORDER__ being
> correctly predefined by the compiler which sparse can then
> pre-process differently from what gcc would, depending on the
> building machine endianness.
> 
> Fix this by letting sparse know about the architecture endianness.
> 
> To: David S. Miller <davem@davemloft.net>
> CC: sparclinux@vger.kernel.org
> Signed-off-by: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
> ---
>  arch/sparc/Makefile | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/arch/sparc/Makefile b/arch/sparc/Makefile
> index 8496a074b..ef1598f5a 100644
> --- a/arch/sparc/Makefile
> +++ b/arch/sparc/Makefile
> @@ -55,6 +55,8 @@ endif
>  
>  endif
>  
> +CHECKFLAGS     += -mbig-endian
> +

You have added a new assignment to CHECKFLAGS because this
options is the same for sparc32 and sparc64, which is fine.

But could you then in the same patch
also move the assingmnet to -D__sparc__ this place, as this is also
a common option for sparc32 and sparc64.
As it is after your patch we have common options duplicated (__sparc__)
and in their own assignment (-mbig-endian).
This is inconsistent and may confuse the next reader.

	Sam

  reply	other threads:[~2017-11-02  5:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-31 17:22 [PATCH] sparc: pass endianness info to sparse Luc Van Oostenryck
2017-11-02  5:41 ` Sam Ravnborg [this message]
2017-11-02  6:14 ` Luc Van Oostenryck

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=20171102054140.GA1454@ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=sparclinux@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.