similar to: Add llvm-mca to CODE_OWNERS.TXT

Makes sense to me, please add it! Thanks again for contributing this work, -Chris > On Apr 18, 2018, at 5:07 AM, Simon Pilgrim via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Please can we add a code owner entry for llvm-mca, which should probably be Andrea. > > I wasn't sure if we need to go through a full nomination process for new tools like this (and

Hi everyone, Can someone help me with running llvm-exegesis tool on x86_64? I saw that I need libpfm library, but I'm still getting segmentation fault when I try to run the tool. Is there anything else I need to do (build llvm on some specific way) ? This is how I tried to run this tool: llvm-exegesis -mode=latency -opcode-name=ADD64rr Thanks, Luka -------------- next part -------------- An

Sounds like a very useful tool.  Thank you for contributing. Taking a step back and looking at the big picture, combining this with the recently contributed llvm-mca dramatically improves our scheduling and performance analysis story.  Being able to take a snippet of code on a particular machine, measure latency/throughput/ports for each instruction (this tool), and then analyze the entire

[You can find an easier to read and more complete version of this RFC here <https://docs.google.com/document/d/1QidaJMJUyQdRrFKD66vE1_N55whe0coQ3h1GpFzz27M/edit?ts=5aaa84ee#> .] Knowing instruction scheduling properties (latency, uops) is the basis for all scheduling work done by LLVM. Unfortunately, vendors usually release only partial (and sometimes incorrect) information. Updating the

Hello, I've been testing llvm-exegesis on X86. Latency and inverse_throughput modes work fine but when I run uops I get an error: event not found - cannot create event uops_dispatched_port:port_0 LLVM ERROR: invalid perf event 'uops_dispatched_port:port_0' I'm running this on a i7-4790K. Am I missing something on my computer or is this not yet fully implemented? This also

On Feb 14, 2014, at 1:09 PM, Howard Hinnant <hhinnant at apple.com> wrote: > Author: hhinnant > Date: Fri Feb 14 15:09:01 2014 > New Revision: 201432 > > URL: http://llvm.org/viewvc/llvm-project?rev=201432&view=rev > Log: Remove myself as owner of libc++ > > Modified: > llvm/trunk/CODE_OWNERS.TXT > > Modified: llvm/trunk/CODE_OWNERS.TXT > URL:

On 03/15/2018 10:04 AM, Guillaume Chatelet via llvm-dev wrote: > [You can find an easier to read and more complete version of this RFC > here > <https://docs.google.com/document/d/1QidaJMJUyQdRrFKD66vE1_N55whe0coQ3h1GpFzz27M/edit?ts=5aaa84ee#>.] > > Knowing instruction scheduling properties (latency, uops) is the basis > for all scheduling work done by LLVM. > > >

On Thu, Mar 15, 2018 at 4:41 PM, Hal Finkel via llvm-dev < llvm-dev at lists.llvm.org> wrote: > > On 03/15/2018 10:04 AM, Guillaume Chatelet via llvm-dev wrote: > > [You can find an easier to read and more complete version of this RFC here > <https://docs.google.com/document/d/1QidaJMJUyQdRrFKD66vE1_N55whe0coQ3h1GpFzz27M/edit?ts=5aaa84ee#> > .] > > Knowing

On Fri, Feb 14, 2014 at 1:29 PM, Howard Hinnant <hhinnant at apple.com> wrote: > On Feb 14, 2014, at 4:23 PM, Marshall Clow <mclow.lists at gmail.com> wrote: > >> On Feb 14, 2014, at 1:09 PM, Howard Hinnant <hhinnant at apple.com> wrote: >> >>> Author: hhinnant >>> Date: Fri Feb 14 15:09:01 2014 >>> New Revision: 201432 >>>

On 18 July 2015 at 00:51, Jim Grosbach <grosbach at apple.com> wrote: > The goal of CODE_OWNERS.txt is to give high level > guidance for who to ask questions of, seek out for code review, find for > partnering up for collaborating on crazy ideas, etc.. The right person for a > great deal of that on LLD+Darwin is Lang, and it would be a shame to have > the official listing not

> On Jul 19, 2015, at 9:01 AM, Chris Lattner <clattner at apple.com> wrote: > >> >> On Jul 19, 2015, at 6:04 AM, Renato Golin <renato.golin at linaro.org> wrote: >> >> On 18 July 2015 at 00:51, Jim Grosbach <grosbach at apple.com> wrote: >>> The goal of CODE_OWNERS.txt is to give high level >>> guidance for who to ask questions

> On May 25, 2016, at 4:17 PM, Andrew Trick via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > I would like to nominate Sanjoy Das as code owner of Scalar Evolution and Induction Variable Simplification. > > Scalar Evolution has never had an official code owner, but does regularly need in depth review. Over the past year and a half, Sanjoy has made fantastic contributions

I am pleased to announce that LLVM 7 is now available. Get it here: https://llvm.org/releases/download.html#7.0.0 The release contains the work on trunk up to SVN revision 338536 plus work on the release branch. It is the result of the community's work over the past six months, including: function multiversioning in Clang with the 'target' attribute for ELF-based x86/x86_64 targets,

I am pleased to announce that LLVM 7 is now available. Get it here: https://llvm.org/releases/download.html#7.0.0 The release contains the work on trunk up to SVN revision 338536 plus work on the release branch. It is the result of the community's work over the past six months, including: function multiversioning in Clang with the 'target' attribute for ELF-based x86/x86_64 targets,

Alex, I have built ubuntu binaries for the last couple of releases. I apologize -- I haven't built those new binaries yet, I only have uploaded the SLES ones. I have an ubuntu 14 tarball that I'll upload today. I will work on getting ubuntu 16 or 17 next. The dpkg/APT repos might be a good substitute, though. Hans, apologies -- I should've asked to hold the 7.0.0 release for

Since the option of running -mode=inverse_throughput was added to llvm-exegesis the names of classes like UopsSnippetGenerator and UopsBenchmarkRunner, that this mode shares with uops, started to be less descriptive. Inverse_throughput doesn't use the uops counters, so for example, the instruction layout shared between these two modes is really connected to parallelism, not uops. It's

Hi all, In a recent IISWC paper <http://groups.csail.mit.edu/commit/papers/19/ithemal-measurement.pdf>, we've proposed BHive - a new methodology for benchmarking arbitrary basic blocks that has several advantages over the one currently used in llvm-exegesis. In particular, the new methodology: - automatically handles memory accesses in the basic block, without the need to manually

Ubuntu 16: a2a2768b04e1d561e6f9a1a2d525eda7aae18624 clang+llvm-7.0.0-x86_64-linux-gnu-ubuntu-16.04.tar.xz On Thu, Sep 20, 2018 at 7:12 PM Brian Cain <brian.cain at gmail.com> wrote: > Uploaded ubuntu 14: > > dec5ca53043c80c1c6e90c0473df84f0182d80af > clang+llvm-7.0.0-x86_64-linux-gnu-ubuntu-14.04.tar.xz > > > On Wed, Sep 19, 2018 at 12:58 PM Brian Cain <brian.cain

I would like to nominate Sanjoy Das as code owner of Scalar Evolution and Induction Variable Simplification. Scalar Evolution has never had an official code owner, but does regularly need in depth review. Over the past year and a half, Sanjoy has made fantastic contributions to SCEV and has been responsive reviewing patches. He is clearly the authority at this point. Induction variable

Hello, Recent code owner activities have led to what I would call loss of referential integrity in the CODE_OWNERS.TXT file. Changes are fine but the information in the CODE_OWNERS.TXT does not allow to positively identify code owner of the particular file or patch. The problem stems from the usage of the "description (D)" field which is overloaded with meaning. Most people put