[PATCH] D66600: Add encode and decode methods to InlineInfo and document encoding format to the GSYM file format

Greg Clayton via Phabricator via llvm-commits llvm-commits at lists.llvm.org
Wed Sep 4 10:29:45 PDT 2019


clayborg marked 3 inline comments as done.
clayborg added inline comments.


================
Comment at: lib/DebugInfo/GSYM/InlineInfo.cpp:127
+  // it will waste space in the GSYM file.
+  if (!isValid())
+    return createStringError(std::errc::invalid_argument,
----------------
aprantl wrote:
> What's the advantage of having invalid InlineInfo objects? Could we just have whoever creates them return a a valid object or an error otherwise?
InlineInfo objects will be created by converting debug info into these objects. So they start out default constructed and then get populated as we parse the attributes. Clients should ensure these objects are valid prior to adding them to a GSYM file or into another InlineInfo object. 


CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D66600/new/

https://reviews.llvm.org/D66600





More information about the llvm-commits mailing list