search for: fission

...gid=513) (pid 2271) ------------------------------------ Here is the output of the rpcclient's enumprinters, The first printer doesn't have the driver installed (and works) whilst the second has the driver installed (and doesn't): rpcclient $> enumprinters 2 servername:[\\fissionator] printername:[\\fissionator\Ricoh] sharename:[Ricoh] portname:[Samba Printer Port] drivername:[] comment:[Ricoh 3245C MFD] location:[] sepfile:[] printprocessor:[winprint] datatype:[RAW] parameters:[] attrib...

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 DWARF. This preserves seman...

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 particularly using it correctly at the moment (given that it was relatively undocumented and I had word of mouth w...

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 under fission, but I >> admittedly don't fully understand it anyway. >> > > So we're not particularly using it correctly at the moment (given that > it was relatively undocumented...

...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 well, so I won't single out ThinLTO here. > > When are the .dwo files produced? If at link time, what is the advantage > of using fission? Normally the advantage is the faster link, but if it > is the linker producing them, wh...

...vm-dev at lists.llvm.org>> wrote: > David Blaikie via llvm-dev <llvm-dev at lists.llvm.org <mailto: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 well, so I won't single out ThinLTO here. > > When are the .dwo files produced? If at link time, what is the advantage > of using fission? Normally the advantage is the faster link, but if it > is the linker producing them, w...

...7 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 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 dist...

>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 wh...

...gt;> wrote: >> >> > On May 3, 2017, at 2:00 PM, David Blaikie <dblaikie at gmail.com <mailto: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 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 p...

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 atmosphe...

...to provide those offsets. But then ref_addr would work across CUs from the same .dwo file. --paulr From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] On Behalf Of David Blaikie via llvm-dev Sent: Wednesday, May 03, 2017 7:52 PM To: Adrian Prantl Cc: llvm-dev Subject: Re: [llvm-dev] DWARF Fission + ThinLTO On Wed, May 3, 2017 at 7:48 PM Adrian Prantl <aprantl at apple.com<mailto:aprantl at apple.com>> wrote: On May 3, 2017, at 7:43 PM, Adrian Prantl via llvm-dev <llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>> wrote: On May 3, 2017, at 2:59 PM, Dav...

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(...

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.

...ost loop because it has better cache locality. This would result in the desired loop order: i, k, j; and LoopInterchange can interchange 'j' and 'k' loops given the legality check passes (a nearest ordering for which legality is correct is also an optimal loop ordering). For fusion/fission, loop costs due to cache can be calculated by assigning cache penalties for references with respect to loops before and after fusion/fission. The costs will be a profitability measure for fusion/fission. I think use case description was very brief in a previous mail. So I have elaborated this time...

...ection headers since they are not needed for loading. This is useful in the same contexts as stripping but some tools and dynamic linkers may be confused by it. This is possibly only valid on ELF unlike general stripping which is a valid option on multiple platforms. 6. Use Case: DWARF fission Who uses it: Clang, Fuchsia, Chromium ```sh objcopy --extract-dwo foo foo.debug objcopy --strip-dwo foo foo ``` [Example use 1]( https://github.com/llvm-mirror/clang/blob/3efd04e48004628cfaffead00ecb1c206b0b6cb2/lib/Driver/ToolChains/CommonArgs.cpp ) [Example use 2]( https:/...

...2: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 relatively non-intrusive > (we build type units once, there's no ambiguity about when they're done) - > for non-fission+type units it might be a bit tricky, because the type units > still need a relocation for the stmt_list* (I'm trying to find where that's > added now... I seem to have lost it), but fission+type units should produce > entirely static type units that are knowable the moment the type...

...t;> >> Hi, >> >> This is a proposal about implementing an analysis that calculates loop >> cost based on cache data. The primary motivation for implementing this is >> to write profitability measures for cache related optimizations like >> interchange, fusion, fission, pre-fetching and others. >> >> I have implemented a prototypical version at >> http://reviews.llvm.org/D21124. >> >> I quick comment on your pass: You'll also want to add the ability to get >> the loop trip count from profiling information from BFI when avai...

...aware Loop Cost Analysis > > Hi, > > This is a proposal about implementing an analysis that calculates loop > cost based on cache data. The primary motivation for implementing this is > to write profitability measures for cache related optimizations like > interchange, fusion, fission, pre-fetching and others. > > I have implemented a prototypical version at > http://reviews.llvm.org/D21124. > > I quick comment on your pass: You'll also want to add the ability to get > the loop trip count from profiling information from BFI when available (by > dividing...

...ore debug info) this will provide a basis for such a state of affairs in the future. > Anyway, to backtracing: > > On Wed, Aug 27, 2014 at 4:40 PM, David Blaikie <dblaikie at gmail.com> wrote: > >> 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 describe...