search for: tinyptrvector

...ping max capacity to 2B)... likely reasonable. > > The patch LGTM, but why would someone actually have a SmallVector with N = 0? Isn’t that a vector? It's a vector that can be passed as a SmallVectorImpl parameter. But yeah, mostly misguided. > Also if you’re not familiar with it, TinyPtrVector is a very useful type for vectors that are highly biased towards 0/1 element and whose elements are pointer size. It was added relatively late in LLVM’s evolution, so I wouldn’t be surprised if there are still smallvectors that should be upgraded. TinyPtrVector is designed for use on the heap. Y...

...Info*, 4u>*>]’: /src/llvm-trunk-dev/include/llvm/ADT/PointerUnion.h:153: instantiated from ‘const PT1* llvm::PointerUnion<PT1, PT2>::getAddrOf() const [with T = llvm::VNInfo*, PT1 = llvm::VNInfo*, PT2 = llvm::SmallVector<llvm::VNInfo*, 4u>*]’ /src/llvm-trunk-dev/include/llvm/ADT/TinyPtrVector.h:63: instantiated from ‘const EltTy* llvm::TinyPtrVector<EltTy>::begin() const [with EltTy = llvm::VNInfo*]’ /src/llvm-trunk-dev/lib/CodeGen/InlineSpiller.cpp:382: instantiated from here /src/llvm-trunk-dev/include/llvm/ADT/PointerIntPair.h:98: warning: dereferencing type-punned pointer...

> On Jun 22, 2018, at 15:18, Reid Kleckner <rnk at google.com> wrote: > > On Thu, Jun 21, 2018 at 9:16 PM Duncan P. N. Exon Smith via llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote: >> Out of curiosity, what brings this up? > > I've noticed that Clang is using more stack recently (we're seeing more crashes from

...BitVector.h" #include "llvm/ADT/Statistic.h" #include "llvm/ADT/StringExtras.h" #include "llvm/ADT/StringMap.h" #include "llvm/ADT/StringRef.h" #include "llvm/ADT/StringSet.h" #include "llvm/ADT/StringSwitch.h" #include "llvm/ADT/TinyPtrVector.h" #include "llvm/ADT/Twine.h" Is this something worth putting effort into? If so, I volunteer. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20170527/4f933182/attachment.html>

On Fri, Dec 11, 2015 at 9:58 AM, Diego Novillo <dnovillo at google.com> wrote: > So, I traced it down to the DenseMaps in class FunctionSamples. I've > replaced them with two std::vector, and the read operation causes the > compiler to grow from 70Mb to 280Mb. With the DenseMaps, reading the > profile causes the compiler to grow from 70Mb to 3Gb. > > Somehow the

...quot; >> #include "llvm/ADT/StringExtras.h" >> #include "llvm/ADT/StringMap.h" >> #include "llvm/ADT/StringRef.h" >> #include "llvm/ADT/StringSet.h" >> #include "llvm/ADT/StringSwitch.h" >> #include "llvm/ADT/TinyPtrVector.h" >> #include "llvm/ADT/Twine.h" >> >> >> Is this something worth putting effort into? If so, I volunteer. >> >> >> >> _______________________________________________ >> LLVM Developers mailing listllvm-dev at lists.llvm.orghttp...

...tringExtras.h" >>>> #include "llvm/ADT/StringMap.h" >>>> #include "llvm/ADT/StringRef.h" >>>> #include "llvm/ADT/StringSet.h" >>>> #include "llvm/ADT/StringSwitch.h" >>>> #include "llvm/ADT/TinyPtrVector.h" >>>> #include "llvm/ADT/Twine.h" >>>> >>>> >>>> Is this something worth putting effort into? If so, I volunteer. >>>> >>>> >>>> >>>> _______________________________________________ &gt...

...ot;llvm/ADT/Statistic.h" > #include "llvm/ADT/StringExtras.h" > #include "llvm/ADT/StringMap.h" > #include "llvm/ADT/StringRef.h" > #include "llvm/ADT/StringSet.h" > #include "llvm/ADT/StringSwitch.h" > #include "llvm/ADT/TinyPtrVector.h" > #include "llvm/ADT/Twine.h" > > > Is this something worth putting effort into? If so, I volunteer. > > > > _______________________________________________ > LLVM Developers mailing listllvm-dev at lists.llvm.orghttp://lists.llvm.org/cgi-bin/mailman/li...

...ude "llvm/ADT/StringExtras.h" >>> #include "llvm/ADT/StringMap.h" >>> #include "llvm/ADT/StringRef.h" >>> #include "llvm/ADT/StringSet.h" >>> #include "llvm/ADT/StringSwitch.h" >>> #include "llvm/ADT/TinyPtrVector.h" >>> #include "llvm/ADT/Twine.h" >>> >>> >>> Is this something worth putting effort into? If so, I volunteer. >>> >>> >>> >> >>> _______________________________________________ >>> LLVM De...

...e 40B, not 64B, although my math error is probably irrelevant.) I'm happy to defer to conventional wisdom here if anyone wants me to (and TBH, I've only been looking at profiles that include debug info, so maybe `sizeof(Function)` matters with -g0). > Have you considered something like TinyPtrVector, for a cost of one pointer when it's not being used? It has higher access costs than SmallVector, but when there's exactly one piece of metadata (the subprogram), it's pretty good. Interesting -- I didn't know we had this! Two reasons it can't be used directly: - Here, the...

...tringExtras.h" >>>> #include "llvm/ADT/StringMap.h" >>>> #include "llvm/ADT/StringRef.h" >>>> #include "llvm/ADT/StringSet.h" >>>> #include "llvm/ADT/StringSwitch.h" >>>> #include "llvm/ADT/TinyPtrVector.h" >>>> #include "llvm/ADT/Twine.h" >>>> >>>> >>>> Is this something worth putting effort into? If so, I volunteer. >>>> >>>> >>>> >>> >>>> ________________________________...

Hello LLVM Developers, We are working on extending currently available register rematerialization to include cases where sequence of multiple instructions is required to rematerialize a value. We had a discussion on this in community mailing list and link is here: http://lists.llvm.org/pipermail/llvm-dev/2016-September/subject.html#104777 >From the above discussion and studying the code we

> On 2015 Apr 14, at 21:46, David Blaikie <dblaikie at gmail.com> wrote: > > On Tue, Apr 14, 2015 at 9:33 PM, Duncan P. N. Exon Smith > <dexonsmith at apple.com> wrote: >> >> `Function` definitions should support `MDNode` attachments, with a >> similar syntax to instructions: >> >> define void @foo() nounwind !attach !0 { >>

...>>>>> #include "llvm/ADT/StringMap.h" >>>>> #include "llvm/ADT/StringRef.h" >>>>> #include "llvm/ADT/StringSet.h" >>>>> #include "llvm/ADT/StringSwitch.h" >>>>> #include "llvm/ADT/TinyPtrVector.h" >>>>> #include "llvm/ADT/Twine.h" >>>>> >>>>> >>>>> Is this something worth putting effort into? If so, I volunteer. >>>>> >>>>> >>>>> >>>> >>>>&...