[all-commits] [llvm/llvm-project] ee0c38: [lldb][AArch64] Add MakeTaggedRanges to MemoryTagM...

[David Spickett via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: ee0c3820f8862aaf39d7ad542672092c35dda266
      https://github.com/llvm/llvm-project/commit/ee0c3820f8862aaf39d7ad542672092c35dda266
  Author: David Spickett <david.spickett at linaro.org>
  Date:   2022-01-26 (Wed, 26 Jan 2022)

  Changed paths:
    M lldb/include/lldb/Target/MemoryTagManager.h
    M lldb/source/Plugins/Process/Utility/MemoryTagManagerAArch64MTE.cpp
    M lldb/source/Plugins/Process/Utility/MemoryTagManagerAArch64MTE.h
    M lldb/unittests/Process/Utility/MemoryTagManagerAArch64MTETest.cpp

  Log Message:
  -----------
  [lldb][AArch64] Add MakeTaggedRanges to MemoryTagManager

This is to be used when you want to know what subranges
of a larger range have memory tagging. Like MakeTaggedRange
but memory without tags is skipped and you get a list of ranges back.

Will be used later by DumpDataExtractor to show memory tags.

MakeTaggedRanges assumes that the memory regions it is
given are sorted in ascending order and do not overlap.
For the current use case where you get regions from
GetMemoryRegions and are on some Linux like OS, this is
reasonable to assume.

I've used asserts to check those conditions. In future
any API binding will check them up front to prevent a crash.

Reviewed By: omjavaid

Differential Revision: https://reviews.llvm.org/D112824