From: Abdul Haleem <abdhalee@linux.vnet.ibm.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
sachinp <sachinp@linux.vnet.ibm.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
ego <ego@linux.vnet.ibm.com>,
mahesh@linux.vnet.ibm.com,
linux-kernel <linux-kernel@vger.kernel.org>,
npiggin@gmail.com
Subject: Re: [linux-next][bisected 1945bc45] build brakes for PowerPC BE configuration on LPAR
Date: Thu, 04 May 2017 16:20:50 +0530 [thread overview]
Message-ID: <1493895050.7355.22.camel@abdul.in.ibm.com> (raw)
In-Reply-To: <8760hgzzh4.fsf@concordia.ellerman.id.au>
On Thu, 2017-05-04 at 20:29 +1000, Michael Ellerman wrote:
> Abdul Haleem <abdhalee@linux.vnet.ibm.com> writes:
>
> > Hi,
> >
> > linux-next build fails on BE config with next-20170424 onwards
> >
> > the patch https://lkml.org/lkml/2017/4/20/994 fixes a similar issue
> > with kvm guest build failure.
> >
> > arch/powerpc/kernel/exceptions-64s.S: Assembler messages:
> > arch/powerpc/kernel/exceptions-64s.S:395: Error: operand out of range
> > (0xffffffffffff8280 is not between 0x0000000000000000 and
> > 0x000000000000ffff)
> > make[1]: *** [arch/powerpc/kernel/head_64.o] Error 1
>
> I couldn't reproduce that.
>
> What toolchain are you using?
I have gcc-4.8.2-1 on Power 6 LPAR running Fedora 20.
Also recreating the same on Power 8 BE LPAR having gcc-4.8.5-11
>
> cheers
>
--
Regard's
Abdul Haleem
IBM Linux Technology Centre
next prev parent reply other threads:[~2017-05-04 10:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-04 9:24 [linux-next][bisected 1945bc45] build brakes for PowerPC BE configuration on LPAR Abdul Haleem
2017-05-04 10:29 ` Michael Ellerman
2017-05-04 10:50 ` Abdul Haleem [this message]
2017-05-04 10:41 ` Nicholas Piggin
2017-05-05 4:10 ` Abdul Haleem
2017-05-05 6:40 ` Nicholas Piggin
2017-05-15 5:06 ` [linux-next, bisected, " Michael Ellerman
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=1493895050.7355.22.camel@abdul.in.ibm.com \
--to=abdhalee@linux.vnet.ibm.com \
--cc=ego@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mahesh@linux.vnet.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=sachinp@linux.vnet.ibm.com \
--cc=sfr@canb.auug.org.au \
/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).