may someday please someone help dethrone the underlord of AI & rise us up
VkFFT – Vulkan Fast Fourier Transform Library
41–50 of 132 posts
Re: VkFFT – Vulkan Fast Fourier Transform Library
#42Earlier quoted context omitted.
You can read off a GPU in 10us, which is just a single sample at 96khz. If your entire stack lived in the GPU, and you're just reading out the result, this is trivial. If you're constantly copying buffers back and forth because some effects are implemented in the CPU and some in the GPU, not so much! It's probably the case that a full stack GPU implementation would blow what we have out of the water, but you'd lose y…
What's the latency for integrated GPUs?
Crystalwell had a shared CPU/GPU L4 cache with ~50ns latency. I don't think there was a programming model where you could bounce data back and forth that fast, but I don't see a reason why the hardware wouldn't be capable of it.
Re: VkFFT – Vulkan Fast Fourier Transform Library
#43Earlier quoted context omitted.
Paragraph 5 of the LGPL version 2.1 states: A program that contains no derivative of any portion of the Library, but is designed to work with the Library by being compiled or linked with it, is called a "work that uses the Library". Such a work, in isolation, is not a derivative work of the Library, and therefore falls outside the scope of this License.
In that case, if header-only is outside the scope of the license, it begs the question why they would pick that license in the first place. But anyways, it doesn't seem clear from the passage how headers fit in, considering that these headers are not just APIs, they contain the implementation themselves.
It doesn't "beg the question" (that being the name of a logical fallacy), but does invite it.
Sometimes LGPL is chosen out of confusion, sometimes symbolically. Whatever the legal demands it does not impose, it would be rude not to honor its intent.
Re: VkFFT – Vulkan Fast Fourier Transform Library
#44Re: VkFFT – Vulkan Fast Fourier Transform Library
#45Earlier quoted context omitted.
Ya, but the important question is can they invert a binary tree on a whiteboard?
Just get a clear whiteboard, draw the binary tree, then flip the whiteboard 180 around the vertical axis so you are now looking through the back of the whiteboard.
Honestly, it's an O(1) solution depending on choice of data structure, possibly constant-factor more efficient through your program depending on language, and if you're programming on a whiteboard it might also arguably be the idiomatic way to do it in that context.
Limited in that you can only have one tree per whiteboard, though.
Re: VkFFT – Vulkan Fast Fourier Transform Library
#46I think this guy will have no problem getting hired. Being conscious enough to push code online works so much better than the CV preparation courses. You know you're on the right path when you are asked to play up your CV abstract than to downplay it. Personally, I would have a hard time hiring anyone without a Github account and less so working in a place where nobody has one.
To me a Gitlab account, instead, would signify superior judgment.
Getting downvoted, but this is no more arbitrary, myopic, and unfair to the applicant than the parent.
Re: VkFFT – Vulkan Fast Fourier Transform Library
#47Earlier quoted context omitted.
Paragraph 5 of the LGPL version 2.1 states: A program that contains no derivative of any portion of the Library, but is designed to work with the Library by being compiled or linked with it, is called a "work that uses the Library". Such a work, in isolation, is not a derivative work of the Library, and therefore falls outside the scope of this License.
I am confused with that paragraph. So if I statically compiled a project with Qt without any modification, does it fall outside the scope of LGPL as well?
IIRC it’s unclear if static linking LGPL is okay, so most people steer clear
Re: VkFFT – Vulkan Fast Fourier Transform Library
#48Re: VkFFT – Vulkan Fast Fourier Transform Library
#49Earlier quoted context omitted.
I am confused with that paragraph. So if I statically compiled a project with Qt without any modification, does it fall outside the scope of LGPL as well?
IIRC it’s unclear if static linking LGPL is okay, so most people steer clear
Static linking is okay and is allowed as a derivative work, but you need to ship object files.
https://www.gnu.org/licenses/gpl-faq.en.html#LGPLStaticVsDyn...
>(1) If you statically link against an LGPLed library, you must also provide your application in an object (not necessarily source) format, so that a user has the opportunity to modify the library and relink the application.
This is covered in sections 6 and 6a of the LGPL 2.1.
Re: VkFFT – Vulkan Fast Fourier Transform Library
#50Earlier quoted context omitted.
IIRC it’s unclear if static linking LGPL is okay, so most people steer clear
Static linking is okay and is allowed as a derivative work, but you need to ship object files. https://www.gnu.org/licenses/gpl-faq.en.html#LGPLStaticVsDyn... >(1) If you statically link against an LGPLed library, you must also provide your application in an object (not necessarily source) format, so that a user has the opportunity to modify the library and relink the application. This is covered in sections 6 and 6a…
So then the OP is a LGPL header-only library, which is always statically compiled in every source. Do we need to do the same thing, and if yes, how we provide an application to allow recompiling?