search for: riss

I have searched around the lists and Google and found this HYPERLINK "http://people.freebsd.org/~pjd/patches/jail_2004120901.patch"http://people. freebsd.org/~pjd/patches/jail_2004120901.patch I was wondering if anyone know of a multiple IP patch that works with FreeBSD 5.4 I really do not understand why this is not included in the standard jail I mean sure jail is handy for

I've been playing with Fred Riss's "line 0" patch for DWARF (https://reviews.llvm.org/D16569) but in adapting it for current trunk, I find the DwarfDebug stuff has been refactored to allow either DWARF or CodeView. That's all good, but the question is whether the "line 0" patch should be DWARF-specific...

...tribute it really doesn't matter which of the 3 (4?) different forms was used as long as the actual string shows up correctly. --paulr From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Eric Christopher Sent: Monday, January 19, 2015 10:54 AM To: Frédéric Riss; David Blaikie Cc: LLVM Developers Mailing List Subject: Re: [LLVMdev] Dropping the DW_ prefix from names in dwarfdump On Mon Jan 19 2015 at 10:42:52 AM Frédéric Riss <friss at apple.com<mailto:friss at apple.com>> wrote: On Jan 19, 2015, at 10:34 AM, David Blaikie <dblaikie at gma...

...ld be something like: DwarfLinker::link(const DebugMap& map); Where the DebugMap is a collection of object files containing debug info associated with symbol mappings. In the end the dsymutil utility should just be a thin command line wrapper around that. > On 11/7/2014 11:53 AM, Frédéric Riss wrote: >>> On Nov 7, 2014, at 9:20 AM, Shankar Easwaran <shankare at codeaurora.org> wrote: >>> >>> Hi Fred, >>> >>> Could this tool be extended to read DWARF information in the final image and then pack it differently for other architectures as...

> On Feb 20, 2015, at 11:14 AM, Duncan P. N. Exon Smith <dexonsmith at apple.com> wrote: > > >> On 2015-Feb-20, at 09:44, Frédéric Riss <friss at apple.com> wrote: >> >> Speaking of deduplication of filenames. I think we discussed that in the early stages of your work, but I just wanted to make sure I remember correctly: the new debug hierarchy will allow to implement specific uniquing behavior, right? So we will...

...parate. In the future, if / when we decide to provide a unified interface (e.g libDebugInfo as you suggest), there will be additional machinery required to wrap the two interfaces, so we could move the DIContext class at that time. Does this make sense? On Thu Jan 29 2015 at 10:54:37 AM Frédéric Riss <friss at apple.com> wrote: > On Jan 29, 2015, at 10:20 AM, Zachary Turner <zturner at google.com> wrote: > > I've been working on adding pdb reading support to llvm. This started as > a tool for dumping info from a pdb (similar to llvm-dwarfdump), which has > been...

...t has run dsymutil on the binary. This is cumbersome and is one of the reasons why the dsymutil link step should really be carried out by lld itself, so that the build system doesn’t need to be aware of that kind of subtelties. Fred > Shankar Easwaran > > On 11/7/2014 10:09 AM, Frédéric Riss wrote: >> Hi, >> >> [ I Cc'd lld people and debug info people. Apologies if I omitted some stakeholder. ] >> >> As stated in the subject, I’d like to start working on an in-tree reimplementation of Darwin’s dsymutil utility. This is an initial step on the path to...

...b, why put the code in LLVM and not only in LLDB? I would love to see LLDB using our Dwarf parser because there is quite some code duplication here, but it wouldn’t be the case for PDB support (again, not an objection, just a candide question). Fred > On Thu Jan 29 2015 at 10:54:37 AM Frédéric Riss <friss at apple.com <mailto:friss at apple.com>> wrote: >> On Jan 29, 2015, at 10:20 AM, Zachary Turner <zturner at google.com <mailto:zturner at google.com>> wrote: >> >> I've been working on adding pdb reading support to llvm. This started as a tool...

.... So CodeView needs to deal with this already, > though I don't know how it currently handles this. > > -- adrian > > > On Aug 17, 2016, at 11:43 AM, Robinson, Paul via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > > > > I've been playing with Fred Riss's "line 0" patch for DWARF > > (https://reviews.llvm.org/D16569) but in adapting it for current trunk, > > I find the DwarfDebug stuff has been refactored to allow either DWARF > > or CodeView. That's all good, but the question is whether the "line 0"...

> On 2015-Jan-19, at 12:38, Frédéric Riss <friss at apple.com> wrote: > > >> On Jan 19, 2015, at 12:04 PM, Christian Schafmeister <chris.schaf at verizon.net> wrote: >> >> >> I forgot to mention this in my initial email. >> >> The build of LLVM that I was using was commit a0d5d7aed...

...gt; > I just noticed the tool is "llvm-dsymutil" but it's in tools/dsymutil, > unlike all the other tools that have the llvm-prefix in the directory name. > Could we move it to "tools/llvm-dsymutil" for consistency? > > On Fri, Nov 7, 2014 at 8:09 AM, Frédéric Riss <friss at apple.com> wrote: > >> Hi, >> >> [ I Cc'd lld people and debug info people. Apologies if I omitted some >> stakeholder. ] >> >> As stated in the subject, I’d like to start working on an in-tree >> reimplementation of Darwin’s dsymutil...

Hi, [ I think I put the most important contributors to the DebugInfo stuff in Cc:. Is there anyone else that I am missing? ] Just a short notice that I am currently working on making llvm-dwarfdump more developer friendly. There are quite a few features in Darwin’s dwarfdump that we find quite useful and that we would like to contribute to llvm-dwarfdump. I have started by augmenting the

(sorry for the duplicate Fred, I failed at reply-all the first time) On Wed, Oct 22, 2014 at 6:33 PM, Frédéric Riss <friss at apple.com> wrote: > > > On Oct 22, 2014, at 4:57 PM, David Blaikie <dblaikie at gmail.com> wrote: > > > > Just working on some of the gmlt+fission debug info stuff and I came > across a comment that might be relevant to reducing the number of distinct...

...AM, Akira Hatanaka via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Can we still check patches into 3.9.1? > >> On Dec 24, 2016, at 1:47 AM, Jeremy Huddleston Sequoia <jeremyhu at apple.com> wrote: >> >> >>> On Dec 23, 2016, at 11:17, Frédéric Riss <friss at apple.com> wrote: >>> >>> >>>> On Dec 22, 2016, at 9:36 PM, Jeremy Huddleston Sequoia via llvm-dev <llvm-dev at lists.llvm.org> wrote: >>>> >>>> 3.9.0 and current release_39 (r90413) have issues with older static asserti...

...dev <llvm-dev at lists.llvm.org> wrote: >> >> Can we still check patches into 3.9.1? >> >>> On Dec 24, 2016, at 1:47 AM, Jeremy Huddleston Sequoia <jeremyhu at apple.com> wrote: >>> >>> >>>> On Dec 23, 2016, at 11:17, Frédéric Riss <friss at apple.com> wrote: >>>> >>>> >>>>> On Dec 22, 2016, at 9:36 PM, Jeremy Huddleston Sequoia via llvm-dev <llvm-dev at lists.llvm.org> wrote: >>>>> >>>>> 3.9.0 and current release_39 (r90413) have issues with...

> On Dec 23, 2016, at 11:17, Frédéric Riss <friss at apple.com> wrote: > > >> On Dec 22, 2016, at 9:36 PM, Jeremy Huddleston Sequoia via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> >> 3.9.0 and current release_39 (r90413) have issues with older static assertion macros like this one from an older li...

Can we still check patches into 3.9.1? > On Dec 24, 2016, at 1:47 AM, Jeremy Huddleston Sequoia <jeremyhu at apple.com> wrote: > > >> On Dec 23, 2016, at 11:17, Frédéric Riss <friss at apple.com> wrote: >> >> >>> On Dec 22, 2016, at 9:36 PM, Jeremy Huddleston Sequoia via llvm-dev <llvm-dev at lists.llvm.org> wrote: >>> >>> 3.9.0 and current release_39 (r90413) have issues with older static assertion macros like this...

...t are your experiences with it and what are the challenges in upstreaming them? * We would really like to start tracking debug info quality the same way we track code size and performance numbers. What are useful metrics for your use-case? See you all at the dev meeting! Adrian Prantl Fred Riss

...anuary 8, 2020 1:49 PM > To: David Blaikie <dblaikie at gmail.com> > Cc: llvm-dev <llvm-dev at lists.llvm.org>; Jonas Devlieghere > <jdevlieghere at apple.com>; Robinson, Paul <paul.robinson at sony.com>; Eric > Christopher <echristo at gmail.com>; Frederic Riss <friss at apple.com> > Subject: Re: Increasing address pool reuse/reducing .o file size in > DWARFv5 > > I think this sounds like a good plan for Linux. I would like to see the > numbers for Darwin (= non-split DWARF) to decide whether we should just > make that the default...

> On May 5, 2016, at 10:08 AM, Reid Kleckner via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > On Wed, May 4, 2016 at 5:07 PM, Quentin Colombet via llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote: > Typically, what I had in mind was things like typos/thinko, that are bugs, that we notice a few minutes after we made the “main”