CLFFT(1)

πŸ“¦
version 2.12.2 Β· 2 versions
  • 2.12.2 Β· debian bookworm, debian trixie, ubuntu jammy, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking (latest)
  • 2.12.2 Β· opensuse-leap 16.0
, in debian bookworm, debian trixie, ubuntu jammy, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking

πŸ’– clFFT-client πŸ’–

okay bestie, listen up β€” this is the manual for clFFT-client, aka the little program that tests all the various options of the OpenCL FFT library across all your devices, dimensions and precisions. it's giving "I stress-test FFTs for fun" energy and honestly? iconic. πŸŽ€


✨ DESCRIPTION ✨

πŸ¦‹ clFFT client command line options:

here's the whole menu, no skips, no cuts, every single one, periodt:

  • -h, --help β€” produces this help message. yes, the classic. ask for help, receive help. πŸ’…
  • -v, --version β€” print out the queryable version information from the clFFT library. lil peek at what version you're running.
  • -i, --clInfo β€” print out queryable information of the OpenCL runtime. spill the tea about your runtime, bestie.
  • -g, --gpu β€” force instantiation of an OpenCL GPU device. making the GPU the main character. πŸ”₯
  • -c, --cpu β€” force instantiation of an OpenCL CPU device. sometimes the CPU just wants a turn too.
  • -a, --all β€” force instantiation of all OpenCL devices. everybody gets invited to the party. 🫢
  • -o, --outPlace β€” out of place FFT transform (default: in place). moving out, but make it math.
  • --double β€” double precision transform (default: single). double the precision, double the drama. ✨
  • --inv β€” backward transform (default: forward). going the other way, lowkey.
  • -d, --dumpKernels β€” the FFT engine will dump generated OpenCL FFT kernels to disk (default: dump off). it's literally journaling. πŸ“
  • -x, --lenX arg (=1024) β€” specify the length of the 1st dimension of a test array.
  • -y, --lenY arg (=1) β€” specify the length of the 2nd dimension of a test array.
  • -z, --lenZ arg (=1) β€” specify the length of the 3rd dimension of a test array.
  • --isX arg (=1) β€” specify the input stride of the 1st dimension of a test array.
  • --isY arg (=0) β€” specify the input stride of the 2nd dimension of a test array.
  • --isZ arg (=0) β€” specify the input stride of the 3rd dimension of a test array.
  • --iD arg (=0) β€” input distance between subsequent sets of data when batch size > 1.
  • --osX arg (=1) β€” specify the output stride of the 1st dimension of a test array.
  • --osY arg (=0) β€” specify the output stride of the 2nd dimension of a test array.
  • --osZ arg (=0) β€” specify the output stride of the 3rd dimension of a test array.
  • --oD arg (=0) β€” output distance between subsequent sets of data when batch size > 1.
  • -b, --batchSize arg (=1) β€” if this value is greater than one, arrays will be used. yes bestie, that's exactly what it says, I'm not editing it, I don't make the rules. πŸ™ˆ
  • -p, --profile arg (=1) β€” time and report the kernel speed of the FFT (default: profiling off). we love a performance report. ⏱️
  • --inLayout arg (=1) β€” layout of input data:
    1. interleaved
    2. planar
    3. hermitian interleaved
    4. hermitian planar
    5. real
  • --outLayout arg (=1) β€” layout of input data:
    1. interleaved
    2. planar
    3. hermitian interleaved
    4. hermitian planar
    5. real

🌈 the receipts

when you run it, you'll see stuff like this:

clFFT runtime version:     2.4.0

and if everything's vibing:

Internal Client Test *****PASS*****

and the API side of things:

clFFT client API version:  2.4.0   April 2015

⚠️ heads up bestie: every one of these options is copied character-for-character, so don't go "fixing" the --outLayout description or the --batchSize wording. that's just how it is. we respect the source. πŸ’œ

anyway that's the whole page β€” this is the CLFFT(1) manual from User Commands, version 2.4.0, dated April 2015. slay, go transform something. πŸ¦‹βœ¨πŸ‘‘