On Wed, 31 Jan 2024 at 10:59, Palmer Dabbelt <palmer@xxxxxxxxxxx> wrote: > > On Wed, 31 Jan 2024 06:39:25 PST (-0800), stefanha@xxxxxxxxx wrote: > > On Tue, 30 Jan 2024 at 14:40, Palmer Dabbelt <palmer@xxxxxxxxxxx> wrote: > >> On Mon, 15 Jan 2024 08:32:59 PST (-0800), stefanha@xxxxxxxxx wrote: > >> I'm not 100% sure this is a sane GSoC idea, as it's a bit open ended and > >> might have some tricky parts. That said it's tripping some people up > >> and as far as I know nobody's started looking at it, so I figrued I'd > >> write something up. > > > > Hi Palmer, > > Your idea has been added: > > https://wiki.qemu.org/Google_Summer_of_Code_2024#RISC-V_Vector_TCG_Frontend_Optimization > > > > I added links to the vector extension specification and the RISC-V TCG > > frontend source code. > > > > Please add concrete tasks (e.g. specific optimizations the intern > > should implement and benchmark) by Feb 21st. Thank you! > > OK. We've got a few examples starting to filter in, I'll keep updating > the bug until we get some nice concrete reproducers for slowdows of > decent vectorized code. Then I'll take a look and what's inside them, > with any luck it'll be simple to figure out which vector instructions > are commonly used and slow -- there's a bunch of stuff in the RVV > translation that doesn't map cleanly, so I'm guessing it'll be in there. > > If that all goes smoothly then I think we should have a reasonably > actionable intern project, but LMK if you were thinking of something > else? That's great! Thanks, Stefan
