similar to: DWARFv5 DW_FORM_implicit_const support in LLVM

Hello all, it looks like we have a bug here but I am not sure. Currently if we have two similar types with implicit_const attributes and different values we end up with only one abbrev in .debug_abbrev section. For example consider two structures: S1 with implicit_const attribute ATTR and value VAL1 and S2 with implicit_const ATTR and value VAL2. The .debug_abbrev section will contain only 1

Thanks, David for updating us. Regarding, mail address, can use anyone{@gmail or @amd}. but sourav0311 at gmail.com works best for me for mailing lists related stuff. Regarding, GDB side of DWARFv5 side of things, we've testing GDB-8.3 WRT DWARFv5 clang and gcc binaries to get better idea of debuggability of clang generated binaries with GDB. Primary motivation being GDB better handling of

Hi llvm-dev, cfe-dev, It's been a while since our team is investigating DebugInfo in LLVM, we're looking forward to contribute and enhance in LLVM DebugInfo. We,'ve been investigating mostly on DWARF-5 aspects -- couple of them to mention-- 1. Language aspects 2. Location mostly optimized out ones 3. DebugInfo conformance to DWARF-5 To avoid getting conflicted with some body

On Wed, Oct 9, 2019 at 11:59 AM Robinson, Paul <paul.robinson at sony.com> wrote: > Welcome Sourabh, > > > > There are many bits of DWARF-5 that haven’t been implemented. > Got a short list, by chance? > I know there is currently no big push within Sony to “fill in the > corners” for v5, as we have been more focused on quality of debug info for > optimized

Hello , Just curios saw dtrace on a presentation from opensolaris. Is there any document what shows how to use dtrace in combination with RMI Thanks for any feedback Rgds Gottfried

Hi, Sorry for the late reply, I was OOO last week. > On Mar 29, 2018, at 3:59 PM, David Blaikie <dblaikie at gmail.com> wrote: > > +Eric Christopher +Adrian Prantl +Jonas Devlieghere (seems Jonas is doing a bunch of debug info work - guessing he's working with you, Adrian?) Yup, I joined Adrian’s team last August. > I'm guessing Eric's the most likely to have

> > I'm guessing Eric's the most likely to have contacts over in GCC land to > maybe bridge the gap when talking about assembly syntax across the two. > Eric - any ideas how best to negotiate this pseudo-standard? (there's > another feature or two I'd like to propose too - at least to standardize > what the syntax /should/ be, even if gas doesn't support it

+Eric Christopher <echristo at gmail.com> +Adrian Prantl <aprantl at apple.com> +Jonas Devlieghere <jdevlieghere at apple.com> (seems Jonas is doing a bunch of debug info work - guessing he's working with you, Adrian?) I'm guessing Eric's the most likely to have contacts over in GCC land to maybe bridge the gap when talking about assembly syntax across the two. Eric

Hello all, I am implementing support for .debug_names section (which is introduced in DWARFv5 standard as replacement for .debug_pubnames and .debug_pubtypes). The question is: should usage of DWARF version 5 force generation of .debug_names instead of .debug_pubnames or we can make it just default behavior and provide user with the interface (cmd switch) to use other DWARFv5 features but

Yep, Wolfgang picked up on the one thing I saw too. This is why I like having people review my stuff. I think it's a bit of a pity that str_offsets_base can point into the middle of a str_offsets contribution in some ways Actually I changed my mind after saying that in the review, and in this writeup I concluded that it cannot do that. str_offsets_base points to the element immediately

>> To pass the MD5 checksum to the assembler, I added a new optional >> clause to the .file directive: >> md5 "checksum" >> where checksum is the 16-byte checksum in hex.  It's quoted because >> the assembler doesn't have a way to parse a 16-byte integer. > > I'd guess, long-term, that's probably not a great motivation for > choosing

Hello all, I noticed that both Windows and OS X version of R have a GUI (Rconsole). Is there a GUI for Linux? I'm running Debian on which the CLI for R works just fine. Regards, - Robert

On Thu, Mar 29, 2018 at 8:27 AM <paul.robinson at sony.com> wrote: > To pass the MD5 checksum to the assembler, I added a new optional clause > to the .file directive: > > md5 "checksum" > > where checksum is the 16-byte checksum in hex. It's quoted because the > assembler doesn't have a way to parse a 16-byte integer. > I'd guess, long-term,

On Thu, Aug 28, 2014 at 11:51 AM, Alexey Samsonov <vonosmas at gmail.com> wrote: > This sounds great. Teaching backend about the -gmlt might help us in > another way: we might enforce full debug info generation in the frontend > for -fsanitize= flags, then rely on some parts of this debug info in > instrumentation passes and prune it before the actual object file >

> -----Original Message----- > From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] On Behalf Of Pieb, > Wolfgang via llvm-dev > Sent: Wednesday, July 05, 2017 6:14 PM > To: llvm-dev at lists.llvm.org > Subject: Re: [llvm-dev] [DWARFv5] Reading the .debug_str_offsets section > > > -----Original Message----- > > From: llvm-dev [mailto:llvm-dev-bounces at

TL;DR: If I'm trying to define new assembler directive syntax to support DWARF v5, it seems like a good idea for all the various assemblers out there in the world to support the same syntax. How would I go about negotiating that syntax with other assembler providers? Is GNU as the only really relevant one? Long version: DWARF v5 introduces a couple of new features in the .debug_line section

There was some discussion about this in D34765, and I had a follow-up chat with Wolfgang separately, plus spent a fair amount of time in reading and thinking today. I thought I would write my understanding all down here so we can reach a common understanding of how it ought to work, and therefore what our code should do. For any non-DWARF-experts who might be interested, in principle this

To pass the MD5 checksum to the assembler, I added a new optional clause to the .file directive: md5 "checksum" where checksum is the 16-byte checksum in hex. It's quoted because the assembler doesn't have a way to parse a 16-byte integer. Also this is the same syntax Reid invented for the CodeView equivalent. To convey the root source filename, I allow the file number on the

tl;dr: in DWARFv5, using DW_AT_ranges even when the range is contiguous reduces linked, uncompressed debug_addr size for optimized builds by 93% and reduces total .o file size (with compression and split) by 15%. It does grow .dwo file size a bit - DWARFv5, no compression, not split shows the net effect if all bytes are equal: -O3 clang binary grows by 0.4%, -O0 clang binary shrinks by 0.1% Should

In an effort to fix inlined information for backtraces under DWARF Fission in the absence of the split DWARF (.dwo) files, I'm planning on adding -gmlt-like data to the .o file, alongside the skeleton CU. Since that will involve teaching the LLVM about -gmlt (moreso than it already has - the debug info LLVM metadata already describes -gmlt for the purposes of omitting pubnames in that case) I