linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Riccardo Magliocchetti <riccardo.magliocchetti@gmail.com>
To: Lin Ming <minggr@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
	Ingo Molnar <mingo@elte.hu>
Subject: Re: compiling of tools/perf fail on x86 64bit kernel and 32bit userspace
Date: Sat, 07 May 2011 16:46:40 +0200	[thread overview]
Message-ID: <4DC55B50.1030108@gmail.com> (raw)
In-Reply-To: <BANLkTikvtJex=fGYw0f6v8pMKhkWmaM2sA@mail.gmail.com>

Hi there,

Il 07/05/2011 06:55, Lin Ming ha scritto:
> On Sat, May 7, 2011 at 12:54 AM, Riccardo Magliocchetti
> <riccardo.magliocchetti@gmail.com>  wrote:
>> Hi,
>>
>> with latest git, i cannot compile perf on 32 bit userspace with a 64 bit
>> kernel.
>>
>> ~/src/linux-2.6/tools/perf$ make
>> PERF_VERSION = 2.6.39.rc6.224.g06d006f
>>     GEN common-cmds.h
>>     * new build flags or prefix
>>     CC perf.o
>>     CC builtin-annotate.o
>>     CC builtin-bench.o
>>     CC bench/sched-messaging.o
>>     CC bench/sched-pipe.o
>>     CC bench/mem-memcpy-x86-64-asm.o
>> bench/../../../arch/x86/lib/memcpy_64.S: Assembler messages:
>> bench/../../../arch/x86/lib/memcpy_64.S:28: Error: bad register name `%rdi'
>> bench/../../../arch/x86/lib/memcpy_64.S:33: Error: invalid instruction
>> suffix for `movs'
>
> Hi,
>
> I just send out a patch to fix this.
> https://lkml.org/lkml/2011/5/7/4
>
> Could you have a try it?

Works fine, thanks!

riccardo

      reply	other threads:[~2011-05-07 14:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-06 16:54 compiling of tools/perf fail on x86 64bit kernel and 32bit userspace Riccardo Magliocchetti
2011-05-07  4:55 ` Lin Ming
2011-05-07 14:46   ` Riccardo Magliocchetti [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=4DC55B50.1030108@gmail.com \
    --to=riccardo.magliocchetti@gmail.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@ghostprotocols.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=minggr@gmail.com \
    --cc=mingo@elte.hu \
    /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).