Petr Kurapov
Petr Kurapov
In case of building the translator separately (not in-tree with llvm), I had to manually provide linking path. We'd probably need to have a proper cmake way of discovering it....
I also had to modify the build script for it to successfully compile llvm12 (hence the second commit)
Actually, after running the command manually, format on save started working. The issue exists only for a new window/project. I'm able to reproduce it when creating a new working directory.
Hi @Galarius, opening a `*.cl` file (for the first time in a newly created folder) doesn't seem to trigger the extension for me either, just FYI.
I observe the same issue with ubuntu 22.04 and an older Folly version.
The support is merged. Will keep the issue open until we have enabled the tests in CI.
@akroviakov, could you please post the preliminary data here as well?
I'm rooting for the approach. I see no reason to linearize the data on the CPU. I also think kernel data sizes should be arbitrary. Here are some thoughts on...
> Quick data on a simple group by 10'000'000 rows: > > ``` > Current multifrag, 2nd run, 20 frags: > 77ms start(16ms) executePlan Execute.cpp:3540 > Current one frag, 2nd...
> Does it mean linear-multifrag can be beneficial only when we have proper runtime/codegen to remove multifrag costs we don't need when running on a single linear chunk? I think...