search for: fissionable

I have an Ubuntu Sever 9.10 setup running Samba as a PDC for a bunch of Windows clients. Everything is functioning perfectly except for the point and print delivery of printer drivers. I have tested this with Ubuntu 9.10's Samba (3.4.0) and two of the Debian Samba packages (3.4.3 and 3.4.5). All seem to demonstrate the same problem. *What works:* Adding a printer and manually installing the

It looks like we only attach the GNU_ranges_base to skeleton CUs, and never use the attribute under non-fission. Is that right? It's not obvious to me why we'd want to only include this under fission, but I admittedly don't fully understand it anyway. - Dave

So Dehao and I have been dealing with some of the nitty gritty details of debug info with ThinLTO, specifically with Fission(Split DWARF). This applies to LTO as well, so I won't single out ThinLTO here. 1) Multiple CUs in a .dwo file Clang/LLVM produces a CU for each original source file - these CUs are kept through IR linking (thin or full) and produced as distinct CUs in the resulting

On Mon, Dec 9, 2013 at 9:47 AM, David Blaikie <dblaikie at gmail.com> wrote: > It looks like we only attach the GNU_ranges_base to skeleton CUs, and > never use the attribute under non-fission. Is that right? It's not > obvious to me why we'd want to only include this under fission, but I > admittedly don't fully understand it anyway. > So we're not

On Mon, Dec 9, 2013 at 11:48 AM, Eric Christopher <echristo at gmail.com> wrote: > On Mon, Dec 9, 2013 at 9:47 AM, David Blaikie <dblaikie at gmail.com> wrote: >> It looks like we only attach the GNU_ranges_base to skeleton CUs, and >> never use the attribute under non-fission. Is that right? It's not >> obvious to me why we'd want to only include this

On Thu, May 4, 2017 at 7:22 AM, Rafael Avila de Espindola via llvm-dev < llvm-dev at lists.llvm.org> wrote: > David Blaikie via llvm-dev <llvm-dev at lists.llvm.org> writes: > > > So Dehao and I have been dealing with some of the nitty gritty details of > > debug info with ThinLTO, specifically with Fission(Split DWARF). > > > > This applies to LTO as

> On May 4, 2017, at 4:53 PM, David Blaikie <dblaikie at gmail.com> wrote: > > Alrighty, a little fuzzy on how best to implement this - Adrian, you've probably got the most context here as to how to wrangle this. > > My first attempt was in IRMover.cpp, IRLinker::linkFunctionBody - after metadata is copied over, create a new subprogram derived from Dst.getSubprogram,

On Wed, May 3, 2017 at 2:09 PM Adrian Prantl <aprantl at apple.com> wrote: > > > On May 3, 2017, at 2:00 PM, David Blaikie <dblaikie at gmail.com> wrote: > > > > So Dehao and I have been dealing with some of the nitty gritty details > of debug info with ThinLTO, specifically with Fission(Split DWARF). > > > > This applies to LTO as well, so I

>I am on PTO, so slow to respond. > >Some items that are left: > >* Debug fission >* Single file debug fission >* Range extension thunks >* All of freebsd links and works >* Very good performance when all that is in Looks we have initial version of debug fusion implemented. r289790, r289810 commits from yesterday did the rest of main job I believe. I do not know what

> On May 3, 2017, at 7:43 PM, Adrian Prantl via llvm-dev <llvm-dev at lists.llvm.org> wrote: > >> >> On May 3, 2017, at 2:59 PM, David Blaikie <dblaikie at gmail.com <mailto:dblaikie at gmail.com>> wrote: >> >> >> >> On Wed, May 3, 2017 at 2:09 PM Adrian Prantl <aprantl at apple.com <mailto:aprantl at apple.com>> wrote:

As the the first review series of "WoW: the earth fission", we invited the chief task of WoW: theesigner Dave "Fargo" Kosak to discuss with you about his views on the mission design about earth fission. Q: And we will talk about the advantages and disadvantages in the region of 80-85 level? We aim to create the global catastrophe atmosphere; we apportioned the top region to

Sorry, trying to catch up a bit late… It sounds like having more than one CU per .dwo is outside of the intention of the DWARF specification (though not explicitly forbidden), since there is an implied 1-1 relationship between skeleton CU and .dwo. There is an explicit 1-1 relationship between skeleton CU and split-full CU (not .dwo). This suggests to me that if you want a .dwo to have multiple

Hi, I am trying to implement my own Loop fission transformations in llvm. But to find circular dependency, i think i have to use LoopDependenceAnalysis. I am using ModulePass. In this pass I am getting LoopInfo and Loops. but when I try to use LoopDependenceAnalysis It throws segmentation fault. the example shows what i want to do : for(int i = 0; i< n ; i++){ s1 : a[i]

Can we convert OpenCL code with device fission to LLVM-IR ? If yes, please guide me. Regs, Barun -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

On Thu, Jun 23, 2016 at 11:34 PM, Adam Nemet <anemet at apple.com> wrote: > > > >> Hi Vikram, >> >> Is the analysis result specific to a loop nest or to a loop nest together >> with a set of reference groups? >> > The result is specific to each loop in the loop nest and the calculations > are based on the references in the loop nest. > >

LLVM already implements its own version of almost all of binutils. The exceptions to this rule are objcopy and strip. This is a proposal to implement an llvm version of objcopy/strip to complete llvm’s binutils. Several projects only use gnu binutils because of objcopy/strip. LLVM itself uses objcopy in fact. Chromium and Fuchsia currently use objcopy as well. If you want to distribute your build

Thanks, I'll look into that. (Though earlier you told me that debug info for types could be extended while walking the IR, so I wouldn't have thought that would have worked.) Peter On Fri, Feb 05, 2016 at 03:52:19PM -0800, David Blaikie wrote: > Will look more closely soon - but I'd really try just writing out type > units to MC as soon as they're done. It should be

On Thu, Jun 23, 2016 at 9:54 AM, Adam Nemet <anemet at apple.com> wrote: > > On Jun 9, 2016, at 9:21 AM, Vikram TV via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > > > > On Wed, Jun 8, 2016 at 10:20 PM, Hal Finkel <hfinkel at anl.gov> wrote: > >> >> ------------------------------ >> >> *From: *"Vikram TV via

On Wed, Jun 8, 2016 at 10:20 PM, Hal Finkel <hfinkel at anl.gov> wrote: > > ------------------------------ > > *From: *"Vikram TV via llvm-dev" <llvm-dev at lists.llvm.org> > *To: *"DEV" <llvm-dev at lists.llvm.org> > *Sent: *Wednesday, June 8, 2016 2:58:17 AM > *Subject: *[llvm-dev] [Proposal][RFC] Cache aware Loop Cost Analysis >

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 >