From: Ingo Molnar <mingo@elte.hu>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@ozlabs.org, Peter Zijlstra <a.p.zijlstra@chello.nl>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6/6] perf_counter: tools: Makefile tweaks for 64-bit powerpc
Date: Wed, 17 Jun 2009 14:08:31 +0200 [thread overview]
Message-ID: <20090617120831.GB26454@elte.hu> (raw)
In-Reply-To: <19000.55666.866148.559620@cargo.ozlabs.ibm.com>
* Paul Mackerras <paulus@samba.org> wrote:
> +++ b/tools/perf/Makefile
> @@ -157,9 +157,21 @@ uname_R := $(shell sh -c 'uname -r 2>/dev/null || echo not')
> uname_P := $(shell sh -c 'uname -p 2>/dev/null || echo not')
> uname_V := $(shell sh -c 'uname -v 2>/dev/null || echo not')
>
> +# If we're on a 64-bit kernel, use -m64
> +ifneq ($(patsubst %64,%,$(uname_M)),$(uname_M))
> + M64 := -m64
> +endif
this is fine.
> +# Don't use -Werror on ppc64; we get warnings due to using
> +# %Lx formats on __u64, which is unsigned long.
> +Werror := -Werror
> +ifeq ($(uname_M),ppc64)
> + Werror :=
> +endif
hm, i dont really like this one - it just adds a special case on an
arch. Why is __u64 unsigned long on powerpc and not unsigned long
long? I thought the whole mess with u64 was fixed there recently and
powerpc too now uses include/asm-generic/int-ll64.h ?
ah, it does this:
/*
* This is here because we used to use l64 for 64bit powerpc
* and we don't want to impact user mode with our change to ll64
* in the kernel.
*/
#if defined(__powerpc64__) && !defined(__KERNEL__)
# include <asm-generic/int-l64.h>
#else
# include <asm-generic/int-ll64.h>
#endif
That's crappy really.
Ingo
next prev parent reply other threads:[~2009-06-17 12:08 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-17 11:50 [PATCH 1/6] perf_counter: powerpc: Enable use of software counters on 32-bit powerpc Paul Mackerras
2009-06-17 11:51 ` [PATCH 2/6] perf_counter: powerpc: Use unsigned long for register and constraint values Paul Mackerras
2009-06-17 11:52 ` [PATCH 3/6] perf_counter: powerpc: Change how processor-specific back-ends get selected Paul Mackerras
2009-06-17 11:53 ` [PATCH 4/6] perf_counter: powerpc: Make powerpc perf_counter code safe for 32-bit kernels Paul Mackerras
2009-06-17 11:53 ` [PATCH 5/6] perf_counter: powerpc: Add processor back-end for MPC7450 family Paul Mackerras
2009-06-17 14:14 ` Kumar Gala
2009-06-17 23:24 ` Paul Mackerras
2009-06-18 12:50 ` Kumar Gala
2009-06-18 21:10 ` Paul Mackerras
2009-06-17 11:54 ` [PATCH 6/6] perf_counter: tools: Makefile tweaks for 64-bit powerpc Paul Mackerras
2009-06-17 12:08 ` Ingo Molnar [this message]
2009-06-17 12:27 ` Paul Mackerras
2009-06-17 13:28 ` Ingo Molnar
2009-06-18 9:13 ` Ingo Molnar
2009-06-19 8:16 ` Paul Mackerras
2009-06-19 16:27 ` Ingo Molnar
2009-06-17 12:04 ` [PATCH 1/6] perf_counter: powerpc: Enable use of software counters on 32-bit powerpc Ingo Molnar
2009-06-17 14:10 ` Kumar Gala
2009-06-17 23:22 ` Paul Mackerras
2009-06-17 14:21 ` Ingo Molnar
2009-06-17 14:24 ` Kumar Gala
2009-06-17 14:27 ` Ingo Molnar
2009-06-18 23:03 ` Benjamin Herrenschmidt
2009-06-20 10:32 ` Ingo Molnar
2009-06-17 23:27 ` Paul Mackerras
2009-06-18 9:04 ` Ingo Molnar
2009-06-18 23:01 ` Benjamin Herrenschmidt
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=20090617120831.GB26454@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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 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).