From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: Fix compilation error while accessing MPIDR_HWID_BITMASK from .S files
Date: Mon, 19 Feb 2018 11:02:39 +0000 [thread overview]
Message-ID: <20180219110238.GA30394@arm.com> (raw)
In-Reply-To: <36bd758c-dd49-edef-cc1a-20f5b43f5011@huawei.com>
Hi John,
On Mon, Feb 19, 2018 at 10:19:35AM +0000, John Garry wrote:
> On 19/02/2018 06:39, Bhupesh Sharma wrote:
> >Since commit e1a50de37860b3a93a9d643b09638db5aff47650 (arm64: cputype:
> >Silence Sparse warnings), compilation of arm64 architecture is broken
> >with the following error messages:
> >
> > AR arch/arm64/kernel/built-in.o
> > arch/arm64/kernel/head.S: Assembler messages:
> > arch/arm64/kernel/head.S:677: Error: found 'L', expected: ')'
> > arch/arm64/kernel/head.S:677: Error: found 'L', expected: ')'
> > arch/arm64/kernel/head.S:677: Error: found 'L', expected: ')'
> > arch/arm64/kernel/head.S:677: Error: junk at end of line, first
> > unrecognized character is `L'
> > arch/arm64/kernel/head.S:677: Error: unexpected characters following
> > instruction at operand 2 -- `movz x1,:abs_g1_s:0xff00ffffffUL'
> > arch/arm64/kernel/head.S:677: Error: unexpected characters following
> > instruction at operand 2 -- `movk x1,:abs_g0_nc:0xff00ffffffUL'
> >
> >This patch fixes the same by using the UL() macro correctly for
> >assigning the MPIDR_HWID_BITMASK macro value.
> >
> >Signed-off-by: Bhupesh Sharma <bhsharma@redhat.com>
> >---
> > arch/arm64/include/asm/cputype.h | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> >diff --git a/arch/arm64/include/asm/cputype.h b/arch/arm64/include/asm/cputype.h
> >index eda8c5f629fc..350c76a1d15b 100644
> >--- a/arch/arm64/include/asm/cputype.h
> >+++ b/arch/arm64/include/asm/cputype.h
> >@@ -20,7 +20,7 @@
> >
> > #define MPIDR_UP_BITMASK (0x1 << 30)
> > #define MPIDR_MT_BITMASK (0x1 << 24)
> >-#define MPIDR_HWID_BITMASK 0xff00ffffffUL
> >+#define MPIDR_HWID_BITMASK UL(0xff00ffffff)
>
> Works for me.
>
> FYI, I am using (old) gcc-linaro-4.8-2015.06-x86_64_aarch64.
Just to confirm: are you saying that this patch fixes the build for you,
or that mainline builds for you and the patch is not needed?
Cheers,
Will
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will.deacon@arm.com>
To: John Garry <john.garry@huawei.com>
Cc: Bhupesh Sharma <bhsharma@redhat.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, bhupesh.linux@gmail.com
Subject: Re: [PATCH] arm64: Fix compilation error while accessing MPIDR_HWID_BITMASK from .S files
Date: Mon, 19 Feb 2018 11:02:39 +0000 [thread overview]
Message-ID: <20180219110238.GA30394@arm.com> (raw)
In-Reply-To: <36bd758c-dd49-edef-cc1a-20f5b43f5011@huawei.com>
Hi John,
On Mon, Feb 19, 2018 at 10:19:35AM +0000, John Garry wrote:
> On 19/02/2018 06:39, Bhupesh Sharma wrote:
> >Since commit e1a50de37860b3a93a9d643b09638db5aff47650 (arm64: cputype:
> >Silence Sparse warnings), compilation of arm64 architecture is broken
> >with the following error messages:
> >
> > AR arch/arm64/kernel/built-in.o
> > arch/arm64/kernel/head.S: Assembler messages:
> > arch/arm64/kernel/head.S:677: Error: found 'L', expected: ')'
> > arch/arm64/kernel/head.S:677: Error: found 'L', expected: ')'
> > arch/arm64/kernel/head.S:677: Error: found 'L', expected: ')'
> > arch/arm64/kernel/head.S:677: Error: junk at end of line, first
> > unrecognized character is `L'
> > arch/arm64/kernel/head.S:677: Error: unexpected characters following
> > instruction at operand 2 -- `movz x1,:abs_g1_s:0xff00ffffffUL'
> > arch/arm64/kernel/head.S:677: Error: unexpected characters following
> > instruction at operand 2 -- `movk x1,:abs_g0_nc:0xff00ffffffUL'
> >
> >This patch fixes the same by using the UL() macro correctly for
> >assigning the MPIDR_HWID_BITMASK macro value.
> >
> >Signed-off-by: Bhupesh Sharma <bhsharma@redhat.com>
> >---
> > arch/arm64/include/asm/cputype.h | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> >diff --git a/arch/arm64/include/asm/cputype.h b/arch/arm64/include/asm/cputype.h
> >index eda8c5f629fc..350c76a1d15b 100644
> >--- a/arch/arm64/include/asm/cputype.h
> >+++ b/arch/arm64/include/asm/cputype.h
> >@@ -20,7 +20,7 @@
> >
> > #define MPIDR_UP_BITMASK (0x1 << 30)
> > #define MPIDR_MT_BITMASK (0x1 << 24)
> >-#define MPIDR_HWID_BITMASK 0xff00ffffffUL
> >+#define MPIDR_HWID_BITMASK UL(0xff00ffffff)
>
> Works for me.
>
> FYI, I am using (old) gcc-linaro-4.8-2015.06-x86_64_aarch64.
Just to confirm: are you saying that this patch fixes the build for you,
or that mainline builds for you and the patch is not needed?
Cheers,
Will
next prev parent reply other threads:[~2018-02-19 11:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-19 6:39 [PATCH] arm64: Fix compilation error while accessing MPIDR_HWID_BITMASK from .S files Bhupesh Sharma
2018-02-19 6:39 ` Bhupesh Sharma
2018-02-19 10:19 ` John Garry
2018-02-19 10:19 ` John Garry
2018-02-19 11:02 ` Will Deacon [this message]
2018-02-19 11:02 ` Will Deacon
2018-02-19 11:12 ` John Garry
2018-02-19 11:12 ` John Garry
2018-02-19 11:19 ` Will Deacon
2018-02-19 11:19 ` Will Deacon
2018-02-19 12:13 ` Catalin Marinas
2018-02-19 12:13 ` Catalin Marinas
2018-02-19 11:26 ` Jan Glauber
2018-02-19 11:26 ` Jan Glauber
2018-02-19 10:58 ` Arnd Bergmann
2018-02-19 10:58 ` Arnd Bergmann
2018-02-22 4:32 ` Viresh Kumar
2018-02-22 4:32 ` Viresh Kumar
2018-02-19 12:09 ` Robin Murphy
2018-02-19 12:09 ` Robin Murphy
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=20180219110238.GA30394@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.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.