[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180413162043.GD6694@tassilo.jf.intel.com>
Date: Fri, 13 Apr 2018 09:20:43 -0700
From: Andi Kleen <ak@...ux.intel.com>
To: Arnaldo Carvalho de Melo <acme@...nel.org>
Cc: Ingo Molnar <mingo@...nel.org>,
Clark Williams <williams@...hat.com>,
linux-kernel@...r.kernel.org, linux-perf-users@...r.kernel.org,
Arnaldo Carvalho de Melo <acme@...hat.com>,
Adrian Hunter <adrian.hunter@...el.com>,
David Ahern <dsahern@...il.com>,
Jin Yao <yao.jin@...ux.intel.com>,
Jiri Olsa <jolsa@...nel.org>,
Martin Liška <mliska@...e.cz>,
Namhyung Kim <namhyung@...nel.org>,
Ravi Bangoria <ravi.bangoria@...ux.vnet.ibm.com>,
Thomas Richter <tmricht@...ux.vnet.ibm.com>,
Wang Nan <wangnan0@...wei.com>
Subject: Re: [PATCH 17/17] perf annotate: Handle variables in 'sub', 'or' and
many other instructions
On Fri, Apr 13, 2018 at 11:01:11AM -0300, Arnaldo Carvalho de Melo wrote:
> From: Arnaldo Carvalho de Melo <acme@...hat.com>
>
> Just like is done for 'mov' and others that can have as source or
> targets variables resolved by objdump, to make them more compact:
>
> - orb $0x4,0x224d71(%rip) # 226ca4 <_rtld_global+0xca4>
> + orb $0x4,_rtld_global+0xca4
That's not equivalent. It could be non rip relative too. You would need
to keep at least the (%rip).
-Andi
Powered by blists - more mailing lists