All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Sudip Mukherjee (Codethink)" <sudipm.mukherjee@gmail.com>
To: Nathan Chancellor <nathan@kernel.org>,
	Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
	"Maciej W. Rozycki" <macro@orcam.me.uk>
Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
	torvalds@linux-foundation.org,
	clang-built-linux <llvm@lists.linux.dev>
Subject: mips maltaup_xpa_defconfig build failure with clang
Date: Tue, 2 Aug 2022 17:35:47 +0100	[thread overview]
Message-ID: <YulSY1pDms0ZyNs9@debian> (raw)

Hi All,

Not sure if it has been reported, mips maltaup_xpa_defconfig fails to
build with clang with the error:

arch/mips/mm/tlbex.c:629:24: error: converting the result of '<<' to a boolean; did you mean '(1 << _PAGE_NO_EXEC_SHIFT) != 0'? [-Werror,-Wint-in-bool-context]
        if (cpu_has_rixi && !!_PAGE_NO_EXEC) {
                              ^
./arch/mips/include/asm/pgtable-bits.h:174:28: note: expanded from macro '_PAGE_NO_EXEC'
# define _PAGE_NO_EXEC          (1 << _PAGE_NO_EXEC_SHIFT)
                                   ^
arch/mips/mm/tlbex.c:2568:24: error: converting the result of '<<' to a boolean; did you mean '(1 << _PAGE_NO_EXEC_SHIFT) != 0'? [-Werror,-Wint-in-bool-context]
        if (!cpu_has_rixi || !_PAGE_NO_EXEC) {
                              ^
./arch/mips/include/asm/pgtable-bits.h:174:28: note: expanded from macro '_PAGE_NO_EXEC'
# define _PAGE_NO_EXEC          (1 << _PAGE_NO_EXEC_SHIFT)
                                   ^

--
Regards
Sudip

             reply	other threads:[~2022-08-02 16:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-02 16:35 Sudip Mukherjee (Codethink) [this message]
2022-08-02 17:59 ` [PATCH] MIPS: tlbex: Explicitly compare _PAGE_NO_EXEC against 0 Nathan Chancellor
2022-08-04 13:58   ` 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=YulSY1pDms0ZyNs9@debian \
    --to=sudipm.mukherjee@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=macro@orcam.me.uk \
    --cc=nathan@kernel.org \
    --cc=torvalds@linux-foundation.org \
    --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 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.