search for: 1736182

...flow might make it difficult (there's > no dbg.phi instruction), but I like the idea of having more explicit > links in the IR, it would be much clearer to interpret what's going > on. > > [0] https://reviews.llvm.org/D69999?id=229790 > [1] https://reviews.llvm.org/D69886#1736182 > [2] Technically dbg.value(undef,...) is the former too, I guess. > > -- > Thanks, > Jeremy

Hey folks, Would you all mind having a bit of a design discussion around the feature both at the DWARF level and the LLVM implementation? It seems like what's currently being proposed/reviewed (based on the DWARF feature as spec'd) is a pretty big change & I'm not sure I understand the motivation, exactly. The core point of my confusion: Why does describing the thing a pointer

...t; no dbg.phi instruction), but I like the idea of having more explicit > >> links in the IR, it would be much clearer to interpret what's going > >> on. > >> > >> [0] https://reviews.llvm.org/D69999?id=229790 > >> [1] https://reviews.llvm.org/D69886#1736182 > >> [2] Technically dbg.value(undef,...) is the former too, I guess. > >> > >> -- > >> Thanks, > >> Jeremy > > > > _______________________________________________ > > LLVM Developers mailing list > > llvm-dev at lists.llvm.org &g...

On Mon, Dec 16, 2013 at 04:16:29PM -0800, Michael Dalton wrote: > Commit 2613af0ed18a ("virtio_net: migrate mergeable rx buffers to page frag > allocators") changed the mergeable receive buffer size from PAGE_SIZE to > MTU-size, introducing a single-stream regression for benchmarks with large > average packet size. There is no single optimal buffer size for all >

On Mon, Dec 16, 2013 at 04:16:29PM -0800, Michael Dalton wrote: > Commit 2613af0ed18a ("virtio_net: migrate mergeable rx buffers to page frag > allocators") changed the mergeable receive buffer size from PAGE_SIZE to > MTU-size, introducing a single-stream regression for benchmarks with large > average packet size. There is no single optimal buffer size for all >