search for: debuginfodwarf

...fly with Shoaib on this subject and he suggested adding code to llvm-objcopy. I briefly looked through the code and from what I can tell, llvm-objcopy doesn't seem to have any DWARF abilities other than compressing DWARF sections. If we do add functionality to llvm-objcopy, are we ok pulling in DebugInfoDWARF and the LLVM object model? AFAICT the code for this tools has its own object file layer which doesn't match the full layer inside of LLVM (llvm::ObjectFile and DWARFContext). Also, no AsmPrinter objects are used in this codebase either. Looking at lld sources, is seems to use the DebugInfoDWAR...

...fly with Shoaib on this subject and he suggested adding code to llvm-objcopy. I briefly looked through the code and from what I can tell, llvm-objcopy doesn't seem to have any DWARF abilities other than compressing DWARF sections. If we do add functionality to llvm-objcopy, are we ok pulling in DebugInfoDWARF and the LLVM object model? AFAICT the code for this tools has its own object file layer which doesn't match the full layer inside of LLVM (llvm::ObjectFile and DWARFContext). Also, no AsmPrinter objects are used in this codebase either. > > llvm-objcopy supports various ad-hoc binary man...

...his subject and he suggested adding code > to llvm-objcopy. I briefly looked through the code and from what I can > tell, llvm-objcopy doesn't seem to have any DWARF abilities other than > compressing DWARF sections. If we do add functionality to llvm-objcopy, are > we ok pulling in DebugInfoDWARF and the LLVM object model? AFAICT the code > for this tools has its own object file layer which doesn't match the full > layer inside of LLVM (llvm::ObjectFile and DWARFContext). Also, no > AsmPrinter objects are used in this codebase either. > > > llvm-objcopy supports variou...

...he suggested adding code >> to llvm-objcopy. I briefly looked through the code and from what I can >> tell, llvm-objcopy doesn't seem to have any DWARF abilities other than >> compressing DWARF sections. If we do add functionality to llvm-objcopy, are >> we ok pulling in DebugInfoDWARF and the LLVM object model? AFAICT the code >> for this tools has its own object file layer which doesn't match the full >> layer inside of LLVM (llvm::ObjectFile and DWARFContext). Also, no >> AsmPrinter objects are used in this codebase either. >> >> >> llvm...

...ing code >>> to llvm-objcopy. I briefly looked through the code and from what I can >>> tell, llvm-objcopy doesn't seem to have any DWARF abilities other than >>> compressing DWARF sections. If we do add functionality to llvm-objcopy, are >>> we ok pulling in DebugInfoDWARF and the LLVM object model? AFAICT the code >>> for this tools has its own object file layer which doesn't match the full >>> layer inside of LLVM (llvm::ObjectFile and DWARFContext). Also, no >>> AsmPrinter objects are used in this codebase either. >>> >&g...

...mory requirements to support fragmented object files ? > > I'm not sure if you're referring to the memory usage at link time or > the disk space required for the inputs, but I posted both those > figures in my original post in this thread. I mean the run-time memory usage of DebugInfoDWARF library. Currently, when Object file is loaded and DWARFContext class is created the DWARFContext references section data from object::ObjectFile: DWARFContext(std::unique_ptr<const DWARFObject> DObj,..) DWARFObjInMemory(const object::ObjectFile &Obj, ...) class DWARFObjInMemory {   c...

The bot failure can be reproduced with: ./bin/llvm-config "--ldflags" "--libs" "--system-libs" all-targets analysis asmparser asmprinter bitreader bitwriter codegen core debuginfodwarf executionengine instrumentation interpreter ipo irreader linker mc mcjit objcarcopts option profiledata scalaropts support target Looking... -- Mehdi > On Feb 12, 2016, at 10:30 AM, Quentin Colombet <qcolombet at apple.com> wrote: > > Hi, > > This may happen because of...

Looks like this problem is also affecting the Go bindings build. http://lab.llvm.org:8011/builders/clang-x86_64-debian-fast/builds/34538/steps/test/logs/stdio Peter On Fri, Feb 12, 2016 at 10:20:50AM -0800, Ahmed Bougacha via llvm-dev wrote: > +Quentin > > > -Ahmed > > On Fri, Feb 12, 2016 at 10:16 AM, Alina Sbirlea via llvm-dev < > llvm-dev at lists.llvm.org>

Hi James, On 05.11.2020 17:59, James Henderson wrote: > (Resending with history trimmed to avoid it getting stuck in moderator > queue). > > Hi Alexey, > > Just an update - I identified the cause of the "Generated debug info > is broken" error message when I tried to build things locally: the > `outStreamer` instance is initialised with the host Triple,

...c > - > [component_0] > -type = Library > -name = ExecutionEngine > -parent = Libraries > -required_libraries = Core MC Object RuntimeDyld Support Target > +type = OptionalLibrary > +name = PerfJITEvents > +parent = ExecutionEngine > +required_libraries = CodeGen Core DebugInfoDWARF Support Object ExecutionEngine > diff --git a/lib/ExecutionEngine/PerfJITEvents/PerfJITEventListener.cpp b/lib/ExecutionEngine/PerfJITEvents/PerfJITEventListener.cpp > new file mode 100644 > index 00000000000..301a8bc70e1 > --- /dev/null > +++ b/lib/ExecutionEngine/PerfJITEvents/Perf...

Having something like this available in tree would definitely be useful. For simplicity, why don't we start with support for the second style? This is the long term useful one and would be a good starting point for getting the code in tree. Can you give a pointer to the patch so that I can assess the rough complexity? If it's simple enough, I'd be happy to help get it reviewed

Hi, On 2016-12-29 13:17:50 -0800, Philip Reames wrote: > Having something like this available in tree would definitely be > useful. Cool. > For simplicity, why don't we start with support for the second style? This > is the long term useful one and would be a good starting point for getting > the code in tree. Works for me. > Can you give a pointer to the patch so that

...ntaxHighlighting.cpp for Release+Asserts build llvm[3]: Compiling PDBInterfaceAnchors.cpp for Release+Asserts build llvm[3]: Compiling PDBSymDumper.cpp for Release+Asserts build llvm[2]: Compiling MCInstrAnalysis.cpp for Release+Asserts build llvm[3]: Building Release+Asserts Archive Library libLLVMDebugInfoDWARF.a make[3]: Leaving directory '/home/NIKHILREDDY/WORK/LLVM_OBJ/lib/DebugInfo/DWARF' make[2]: Entering directory '/home/NIKHILREDDY/WORK/LLVM_OBJ/lib/IRReader' llvm[3]: Compiling PDBSymbol.cpp for Release+Asserts build llvm[2]: Compiling IRReader.cpp for Release+Asserts build llvm[2]:...