public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
Cc: Adrian Hunter <adrian.hunter@intel.com>, linux-kernel@vger.kernel.org
Subject: Re: Build failure due to Intel PT
Date: Mon, 24 Aug 2015 17:04:58 -0300	[thread overview]
Message-ID: <20150824200458.GD19203@kernel.org> (raw)
In-Reply-To: <20150824185131.GA6606@us.ibm.com>

Em Mon, Aug 24, 2015 at 11:51:31AM -0700, Sukadev Bhattiprolu escreveu:
> 
> I am trying to build perf tool on Powerpc and get this:
> 
> util/intel-pt-decoder/intel-pt-insn-decoder.c: In function ‘intel_pt_insn_decoder’:
> util/intel-pt-decoder/intel-pt-insn-decoder.c:138:3: error: switch missing default case [-Werror=switch-default]
>    switch (insn->immediate.nbytes) {
>    ^
> cc1: all warnings being treated as errors

> Besides adding a 'default' case, can this file be skipped when building on
> non-x86 architectures?

Not sure, what about processing a perf.data file generated on a x86
system using a PowerPC workstation?

Adrian, I am assuming this is only used when postprocessing, is that
right?

- Arnaldo
 
> I am on the perf/core branch, with HEAD pointing to:
> 
> 	commit c0b4dffbc529244d3e4e3bd392f2bffa2d8531a7
> 	Author: Arnaldo Carvalho de Melo <acme@redhat.com>
> 	Date:   Mon Aug 24 13:33:14 2015 -0300
> 
> 	perf annotate: Reset the dso find_symbol cache when removing symbols
> 
> Sukadev

  reply	other threads:[~2015-08-24 20:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-24 18:51 Build failure due to Intel PT Sukadev Bhattiprolu
2015-08-24 20:04 ` Arnaldo Carvalho de Melo [this message]
2015-08-24 20:41   ` Sukadev Bhattiprolu
2015-08-25  7:20   ` Adrian Hunter
2015-08-25 11:35     ` Arnaldo Carvalho de Melo
2015-08-25 11:41       ` Adrian Hunter
2015-08-25 14:24         ` 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=20150824200458.GD19203@kernel.org \
    --to=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sukadev@linux.vnet.ibm.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