From: Akemi Yagi <amyagi@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] perf tools: Fix a misuse of for_each_set_bit() in session.c
Date: Tue, 18 Dec 2012 17:39:06 +0000 (UTC) [thread overview]
Message-ID: <kaq9nq$sot$1@ger.gmane.org> (raw)
In-Reply-To: 20120827161815.4a1a84c7@feng-i7
On Mon, 27 Aug 2012 16:18:15 +0800, Feng Tang wrote:
> It's a compile error:
>
> cc1: warnings being treated as errors util/session.c: In function
> ‘perf_session_deliver_event’: util/include/linux/bitops.h:104: error:
> dereferencing pointer ‘p’ does break strict-aliasing rules
> util/include/linux/bitops.h:96: error: dereferencing pointer ‘p’ does
> break strict-aliasing rules util/session.c:907: note: initialized from
> here util/include/linux/bitops.h:96: note: initialized from here make:
> *** [util/session.o] Error 1
> make: *** Waiting for unfinished jobs....
>
> Casting the @mask to (void *) still sees the same error
>
> Thanks,
> Feng
We (ELRepo) are seeing the same error while building kernel 3.7 for RHEL
6.3 on a 32-bit system. The perf package would build fine if we run
rpmbuild with the 'i686' target specified on a 64-bit system.
http://elrepo.org/bugs/view.php?id=335
Akemi
prev parent reply other threads:[~2012-12-18 17:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-27 7:38 [PATCH 0/3] perf tools: Fixes for some compile errors Feng Tang
2012-08-27 7:38 ` [PATCH 1/3] perf tools: Fix a compiling error in trace-event-perl.c for 32 bits machine Feng Tang
2012-08-27 15:33 ` Arnaldo Carvalho de Melo
2012-08-28 2:17 ` [PATCH v2 " Feng Tang
2012-09-27 4:22 ` [tip:perf/core] " tip-bot for Feng Tang
2012-08-27 7:38 ` [PATCH 2/3] Perf tools: Fix a compiling error in util/map.c Feng Tang
2012-09-27 4:23 ` [tip:perf/core] perf " tip-bot for Feng Tang
2012-08-27 7:38 ` [PATCH 3/3] perf tools: Fix a misuse of for_each_set_bit() in session.c Feng Tang
2012-08-27 7:59 ` Namhyung Kim
2012-08-27 8:18 ` Feng Tang
2012-12-18 17:39 ` Akemi Yagi [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='kaq9nq$sot$1@ger.gmane.org' \
--to=amyagi@gmail.com \
--cc=linux-kernel@vger.kernel.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