From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Vinson Lee <vlee@twopensource.com>
Cc: linux-next@vger.kernel.org,
"Peter Zijlstra" <a.p.zijlstra@chello.nl>,
"Ingo Molnar" <mingo@redhat.com>,
"Andi Kleen" <ak@linux.intel.com>,
"Adrian Hunter" <adrian.hunter@intel.com>,
"Jiri Olsa" <jolsa@kernel.org>, "Rabin Vincent" <rabin@rab.in>,
"Martin Liška" <mliska@suse.cz>
Subject: Re: next-20151007 perf build error "tools/include/linux/compiler.h:66: error: dereferencing pointer ‘res.41’ does break strict-aliasing rules"
Date: Wed, 7 Oct 2015 15:47:32 -0300 [thread overview]
Message-ID: <20151007184732.GF14409@kernel.org> (raw)
In-Reply-To: <CAHTgTXXzH7id6qrpG1qvR8BsKPjny4+kjcvnA1zS6OaMx-+TtA@mail.gmail.com>
Em Wed, Oct 07, 2015 at 11:28:26AM -0700, Vinson Lee escreveu:
> Hi.
>
> I hit this perf build error with next-20151007 with GCC 4.4.
Will check.
> CC util/annotate.o
> cc1: warnings being treated as errors
> util/annotate.c: In function ‘disasm__purge’:
> linux-next/tools/include/linux/compiler.h:66: error: dereferencing
> pointer ‘res.41’ does break strict-aliasing rules
> linux-next/tools/include/linux/compiler.h:66: note: initialized from here
> util/annotate.c: In function ‘symbol__annotate’:
> linux-next/tools/include/linux/compiler.h:66: error: dereferencing
> pointer ‘res.41’ does break strict-aliasing rules
> linux-next/tools/include/linux/compiler.h:66: note: initialized from here
> linux-next/tools/include/linux/compiler.h:52: error: dereferencing
> pointer ‘res.32’ does break strict-aliasing rules
> linux-next/tools/include/linux/compiler.h:52: note: initialized from here
>
> Cheers,
> Vinson
next prev parent reply other threads:[~2015-10-07 18:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-07 18:28 next-20151007 perf build error "tools/include/linux/compiler.h:66: error: dereferencing pointer ‘res.41’ does break strict-aliasing rules" Vinson Lee
2015-10-07 18:47 ` Arnaldo Carvalho de Melo [this message]
2015-10-08 9:12 ` Jiri Olsa
2015-10-13 0:48 ` Vinson Lee
2015-10-13 8:52 ` [PATCH] tools include: Fix strict-aliasing rules breakage " Jiri Olsa
2015-10-13 14:44 ` Arnaldo Carvalho de Melo
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=20151007184732.GF14409@kernel.org \
--to=acme@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mliska@suse.cz \
--cc=rabin@rab.in \
--cc=vlee@twopensource.com \
/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).