From: Masami Hiramatsu <mhiramat@kernel.org>
To: Baruch Siach <baruch@tkos.co.il>
Cc: Robin Murphy <robin.murphy@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [BUG] arm64: Build error with gcc 6
Date: Sun, 25 Feb 2018 20:00:09 +0900 [thread overview]
Message-ID: <20180225200009.80ba37b7837f9f1fb34f64fb@kernel.org> (raw)
In-Reply-To: <20180225051440.7d4ab5ajbb7lhdcr@sapphire.tkos.co.il>
On Sun, 25 Feb 2018 07:14:44 +0200
Baruch Siach <baruch@tkos.co.il> wrote:
> Hi Masami Hiramatsu,
>
> On Sun, Feb 25, 2018 at 11:50:37AM +0900, Masami Hiramatsu wrote:
> > commit e1a50de37860 ("arm64: cputype: Silence Sparse warnings")
> > introduces "UL" suffix to a hex number, but it causes a build error with gcc-6 series.
> > I've hit below error with 6.2.1 and 6.4.1. Of course this is resolved by the latest
> > stable gcc-7.2.1. But from the compatibility point of view, should we revert it?
> >
> > AS arch/arm64/kernel/head.o
> > /home/mhiramat/ksrc/linux/arch/arm64/kernel/head.S: Assembler messages:
> > /home/mhiramat/ksrc/linux/arch/arm64/kernel/head.S:677: Error: found 'L', expected: ')'
> > /home/mhiramat/ksrc/linux/arch/arm64/kernel/head.S:677: Error: found 'L', expected: ')'
> > /home/mhiramat/ksrc/linux/arch/arm64/kernel/head.S:677: Error: found 'L', expected: ')'
> > /home/mhiramat/ksrc/linux/arch/arm64/kernel/head.S:677: Error: junk at end of line, first unrecognized character is `L'
> > /home/mhiramat/ksrc/linux/arch/arm64/kernel/head.S:677: Error: unexpected characters following instruction at operand 2 -- `movz x1,:abs_g1_s:0xff00ffffffUL'
> > /home/mhiramat/ksrc/linux/arch/arm64/kernel/head.S:677: Error: unexpected characters following instruction at operand 2 -- `movk x1,:abs_g0_nc:0xff00ffffffUL'
> > make[2]: *** [/home/mhiramat/ksrc/linux/scripts/Makefile.build:425: arch/arm64/kernel/head.o] error 1
> >
> > I've checked with below 2 latest gccs.
> >
> > http://releases.linaro.org/components/toolchain/binaries/latest-6/aarch64-linux-gnu/gcc-linaro-6.4.1-2017.11-x86_64_aarch64-linux-gnu.tar.xz
> >
> > http://releases.linaro.org/components/toolchain/binaries/latest-7/aarch64-linux-gnu/gcc-linaro-7.2.1-2017.11-x86_64_aarch64-linux-gnu.tar.xz
>
> The fix is pending:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git/commit/?h=fixes/core&id=04c4927359b1f09310bfee92e7187c9022be3e00
>
> This is in Linus' tree now, so should be in -rc3.
Great! I used linux-next tree and hit above bug, so I'll use linus tree.
Thank you,
--
Masami Hiramatsu <mhiramat@kernel.org>
prev parent reply other threads:[~2018-02-25 11:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-25 2:50 [BUG] arm64: Build error with gcc 6 Masami Hiramatsu
2018-02-25 5:14 ` Baruch Siach
2018-02-25 11:00 ` Masami Hiramatsu [this message]
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=20180225200009.80ba37b7837f9f1fb34f64fb@kernel.org \
--to=mhiramat@kernel.org \
--cc=baruch@tkos.co.il \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=will.deacon@arm.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 NNTP newsgroup(s).