Fuzzer test was showing an out-of-bounds accesss on a repeated field somewhere in `ReadNonHeaderEventDataWithoutHeader`. Staring at the code found this one.

PiperOrigin-RevId: 713486488

Becuase of some (very) legacy perf behavior, quipper could ignore the number of PMU mappings and continue reading past them.
Remove that, since perf has been writing the number of mappings reliably since 4.14. This way, we can safely ignore checking against the PERF_RECORD_FEATURE size.
And that allows us to handle padding at the end of the event.

PiperOrigin-RevId: 713351371

Code that we import via MODULE.bazel generates warnings that
are not really actionable from this projects' perspective.
Use new bazel6+ feature to set different options for files matching a
regex, in this case all external/ files shall have switched-off warnings.

Also: explicitly give the -xc++ option for c++ files. Bazel does
not invoke `clang++` but the generic `clang` driver for all files and
hopes that it auto-detects the file. This is not true for all
clang installations, and in particular clangd, clang-tidy etc. have
issues not knowing the type of file.
PiperOrigin-RevId: 693428479

Further slice the L3 hits to local, near, and far L3.

PiperOrigin-RevId: 689060853

PiperOrigin-RevId: 688756974

Any remaining bytes are event IDs. But if the declared payload size is smaller,
subtracting these unsigned values when computing the number of IDs yields a very
large number, which subsequently leads to a memory allocation failure.

PiperOrigin-RevId: 688313672

PiperOrigin-RevId: 687359582

PiperOrigin-RevId: 684574518

PiperOrigin-RevId: 684550232

Update comment to mention keeping filename->buildID to handle the situation where buildid-mmap is not available in perf_data_converter/quipper

PiperOrigin-RevId: 682419195

PiperOrigin-RevId: 680288149

PiperOrigin-RevId: 679361251

PiperOrigin-RevId: 675230254

Bzlmod automatically handles transitive dependencies. We don't use it anywhere within perf_data_converter, so we can safely remove it.

PiperOrigin-RevId: 675211560

Bzlmod automatically handles transitive dependencies. We don't use it anywhere within perf_data_converter, so we can safely remove it.

PiperOrigin-RevId: 675197961

In bzlmod, all direct dependencies are "pinned". This behavior is desired to guarantee version stability; it would be weird if commit hash abcdef123 suddenly doesn't build because one of its dependencies released a new, backwards-incompatible version.

However, bzlmod handles transitive dependencies automatically, so you only have to think about what version *you* specifically need. When you need an API introduced by a new version of your dependency, you just bump your dependency to that version.

The caveat is that library maintainers must bump their compatibility level when they introduce a change that isn't backwards-compatible.

PiperOrigin-RevId: 675180828

PiperOrigin-RevId: 673610716

PiperOrigin-RevId: 673502270

PiperOrigin-RevId: 673102808

PiperOrigin-RevId: 673073337

PiperOrigin-RevId: 669350670

PiperOrigin-RevId: 668565523

PiperOrigin-RevId: 663807973

PiperOrigin-RevId: 662957586

Add code to handle read_format lost field in PerfSampleDataWriter::Write, and fix a bug to read id under group instead of one when PERF_FORMAT_GROUP is set.

PiperOrigin-RevId: 662662435

PiperOrigin-RevId: 656211182

PiperOrigin-RevId: 655748707

PiperOrigin-RevId: 655741186

PiperOrigin-RevId: 655735390

PiperOrigin-RevId: 643155348

Distinguish between `cache_latency` and `total_latency` coming from x86 machines with WEIGHT or WEIGHT_STRUCT.

Both newer Intel machines and AMD machines with IBS populate both fields, so we propagate them accordingly as Profile proto labels.
Older Intel machines only populated the `weight` field, with the "total" issue-to-retirement latency, but we mistakenly used to convert that to `cache_latency`, now
it is in `total_latency`.

PiperOrigin-RevId: 641530291

PiperOrigin-RevId: 641455581

PiperOrigin-RevId: 634592878

* Add quipper support for PERF_RECORD_KSYMBOL event.

PiperOrigin-RevId: 628137192

* Enable quipper parsing of HEADER_GROUP_DESC for PERF_RECORD_HEADER_FEATURE events.

PiperOrigin-RevId: 631961661

---------

Co-authored-by: ghanz <ghanz@google.com>
Co-authored-by: skanev <skanev@google.com>

Also, remove RE2, which is not used anywhere

PiperOrigin-RevId: 613328339

PiperOrigin-RevId: 613322124

 * The warning silenced referencs zlib that had this warning fixed in 1.3
    * while at it: get latest 1.3.1 version.
    * Move _before_ protobuf, so that we actually see the latest version.
 * Instead, silence warnings about signed compare, which is
   a deliberate choice in this code-base.
 * Add an optionally loaded user.bazelrc as that is very useful
   to add local options.
   Best practice documented in https://bazel.build/configure/best-practices#bazelrc-file

PiperOrigin-RevId: 613316337

PiperOrigin-RevId: 612547901

PiperOrigin-RevId: 605448170

PiperOrigin-RevId: 603122760