lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 12 May 2017 07:55:13 -0700 From: Andi Kleen <andi@...stfloor.org> To: Milian Wolff <milian.wolff@...b.com> Cc: Namhyung Kim <namhyung@...nel.org>, linux-kernel@...r.kernel.org, linux-perf-users@...r.kernel.org, Arnaldo Carvalho de Melo <acme@...hat.com>, David Ahern <dsahern@...il.com>, Peter Zijlstra <a.p.zijlstra@...llo.nl>, Yao Jin <yao.jin@...ux.intel.com>, kernel-team@....com Subject: Re: [PATCH v2] perf report: distinguish between inliners in the same function Milian Wolff <milian.wolff@...b.com> writes: > > I think I'm missing something, but isn't this what this function provides? The > function above is now being used by the match_chain_inliner function below. > > Ah, or do you mean for code such as this: > > ~~~~~ > inline_func_1(); inline_func_2(); This could be handled by looking at columns or discriminators too (which some compilers generate in dwarf). srcline.c would need to be changed to also call bfd_get_nearest_discriminator() and pass that extra information everywhere. -Andi
Powered by blists - more mailing lists