linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Paul Mackerras <paulus@samba.org>,
	linuxppc-dev@lists.ozlabs.org, linux-next@vger.kernel.org,
	linux-kernel@vger.kernel.org, Anton Blanchard <anton@samba.org>
Subject: Re: linux-next: build failure after merge of the final tree (powerpc tree related)
Date: Fri, 03 Dec 2010 16:59:58 +1100	[thread overview]
Message-ID: <1291355998.32570.417.camel@pasglop> (raw)
In-Reply-To: <20101203163206.72258fb8.sfr@canb.auug.org.au>

On Fri, 2010-12-03 at 16:32 +1100, Stephen Rothwell wrote:
> 
> After merging the  tree, today's linux-next build (powerpc allmodconfig)
> failed like this:
> 
> arch/powerpc/lib/hweight_64.S: Assembler messages:
> arch/powerpc/lib/hweight_64.S:52: Error: Unrecognized opcode: `popcntw'
> arch/powerpc/lib/hweight_64.S:77: Error: Unrecognized opcode: `popcntw'
> arch/powerpc/lib/hweight_64.S:106: Error: Unrecognized opcode: `popcntd'
> 
> This is with:
> 
> powerpc64-linux-gcc (GCC) 4.4.0
> GNU assembler (GNU Binutils) 2.19.1
> 
> Caused by commit 64ff31287693c1f325cb9cb049569c1611438ef1 ("powerpc: Add
> support for popcnt instructions"). 


This toolchain is a bit ancient I suppose... Anton, do you reckon we
should use .long based macros for these for the time being or just
require a newer binutils ?

Cheers,
Ben.

  reply	other threads:[~2010-12-03  6:00 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-03  5:32 linux-next: build failure after merge of the final tree (powerpc tree related) Stephen Rothwell
2010-12-03  5:59 ` Benjamin Herrenschmidt [this message]
2010-12-03  6:08   ` Stephen Rothwell
2010-12-03 11:26   ` Josh Boyer
2011-03-14  9:38 Stephen Rothwell
2011-03-14 20:37 ` Benjamin Herrenschmidt
2011-03-14 20:51   ` David Miller
2011-03-14 21:17     ` Thomas Gleixner
2011-03-14 21:21   ` Lennert Buytenhek
2011-05-05  3:41 Stephen Rothwell
2011-06-30  6:36 Stephen Rothwell
2011-06-30  7:09 ` Benjamin Herrenschmidt
2012-09-06  7:11 Stephen Rothwell
2012-09-06  8:20 ` Ananth N Mavinakayanahalli
2013-01-11  5:52 Stephen Rothwell
2013-01-11  6:04 ` Michael Neuling
2013-12-09  6:32 Stephen Rothwell

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=1291355998.32570.417.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=anton@samba.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=paulus@samba.org \
    --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).