search for: llvm_dump

...getCachedResult<DumpAccumulator>(M); Then dump messages: if (DAR) { DAR->Message += "Processing "; DAR->Message += F.getName(); DAR->Message += "\n"; } AsmPrinter ---------- We dump the messages from DumpAccumulator into a section called ".llvm_dump" in a compressed manner. Specifically, the section contains: - LEB128 encoding of the original size in bytes - LEB128 encoding of the compressed size in bytes - the message compressed by zlib::compressed in that order. llvm-readobj ------------ We read the .llvm_dump section. We dump eac...

...uild), you have to collect those files and concatenate them, and modify the build system to be aware of all that. > > I’m not sure it’s helpful to have a generic mechanism for this; it’s not > clear how this would work if multiple different features were trying to > emit data into the llvm_dump section at the same time. > You could layer the approach: the one llvm_dump section has a pluggable reader. > > > -Eli > > > > *From:* llvm-dev <llvm-dev-bounces at lists.llvm.org> *On Behalf Of *Kazu > Hirata via llvm-dev > *Sent:* Wednesday, August 5, 2020 3...

...DAR->Message += "Processing "; >>      DAR->Message += F.getName(); >>      DAR->Message += "\n"; >>    } >> >> AsmPrinter >> ---------- >> >> We dump the messages from DumpAccumulator into a section called >> ".llvm_dump" in a compressed manner.  Specifically, the section >> contains: >> >> - LEB128 encoding of the original size in bytes >> - LEB128 encoding of the compressed size in bytes >> - the message compressed by zlib::compressed >> >> in that order. >> &g...