Skip to content
Snippets Groups Projects
Select Git revision
  • 2df1083e38ade327c0668ee22ac2c843b2ab57af
  • master default protected
  • add-clFFT_GetSize
  • add-dylib-target
  • counting-mallocs
  • remove-CPU-constraint
  • Add-PKGBUILD
  • HSA
  • clmathfft
  • longer_dft_support
  • current_fgrp_apps
  • current_brp_apps
12 results

fft_base_kernels.h

Blame
  • Forked from einsteinathome / libclfft
    Source project has a limited visibility.
    • Heinz-Bernd Eggenstein's avatar
      20314512
      Bug #1608: clFFT use of native_sin , native_cos can cause validation problems · 20314512
      Heinz-Bernd Eggenstein authored
      experimental: -added alternative method for twiddle factor calc, using a smaller LUT (256 * float2 )
                     via Taylor series to 3rd order, seems to be almost as accurate as method with 2 bigger LUTs, but faster.
                    -improved method w/ 2 bigger LUTs to use LUTs of float2
                    -improved method using slow sin/cos functions (now uses sincos combined function), still slow
                    - preparaed plan struct to have method switchable at plan creation time.
      
                    TODO: load smaller LUT for Taylor series approx into shared mem.
      20314512
      History
      Bug #1608: clFFT use of native_sin , native_cos can cause validation problems
      Heinz-Bernd Eggenstein authored
      experimental: -added alternative method for twiddle factor calc, using a smaller LUT (256 * float2 )
                     via Taylor series to 3rd order, seems to be almost as accurate as method with 2 bigger LUTs, but faster.
                    -improved method w/ 2 bigger LUTs to use LUTs of float2
                    -improved method using slow sin/cos functions (now uses sincos combined function), still slow
                    - preparaed plan struct to have method switchable at plan creation time.
      
                    TODO: load smaller LUT for Taylor series approx into shared mem.
    editinfo 1.00 KiB
    # The "editinfo" file is used to allow verification of logging
    # information.  It works best when a template (as specified in the
    # rcsinfo file) is provided for the logging procedure.  Given a
    # template with locations for, a bug-id number, a list of people who
    # reviewed the code before it can be checked in, and an external
    # process to catalog the differences that were code reviewed, the
    # following test can be applied to the code:
    #
    #   Making sure that the entered bug-id number is correct.
    #   Validating that the code that was reviewed is indeed the code being
    #       checked in (using the bug-id number or a seperate review
    #       number to identify this particular code set.).
    #
    # If any of the above test failed, then the commit would be aborted.
    #
    # Actions such as mailing a copy of the report to each reviewer are
    # better handled by an entry in the loginfo file.
    #
    # One thing that should be noted is the the ALL keyword is not
    # supported.  There can be only one entry that matches a given
    # repository.