Update to the latest internal version #180
Merged
+980
−103
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
PiperOrigin-RevId: 684574518
PiperOrigin-RevId: 687359582
… size of the event payload. 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: 688756974
… AMD ZEN4. Further slice the L3 hits to local, near, and far L3. PiperOrigin-RevId: 689060853
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
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
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
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
gmarin13
approved these changes
Jan 15, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.