API Reference

API Reference#

file rocfft.h

rocfft.h defines all the public interfaces and types

Defines

ROCFFT_EXPORT#

Typedefs

typedef struct rocfft_plan_t *rocfft_plan#

Pointer type to plan structure.

This type is used to declare a plan handle that can be initialized with rocfft_plan_create.

typedef struct rocfft_plan_description_t *rocfft_plan_description#

Pointer type to plan description structure.

This type is used to declare a plan description handle that can be initialized with rocfft_plan_description_create.

typedef struct rocfft_execution_info_t *rocfft_execution_info#

Pointer type to execution info structure.

This type is used to declare an execution info handle that can be initialized with rocfft_execution_info_create.

typedef struct rocfft_field_t *rocfft_field#

Pointer type to a rocFFT field structure.

rocFFT fields are used to hold data decomposition information which is then passed to a rocfft_plan via a rocfft_plan_description

Warning

Experimental! This feature is part of an experimental API preview.

typedef struct rocfft_brick_t *rocfft_brick#

Pointer type to a rocFFT brick structure.

rocFFT bricks are used to describe the data decomposition of fields.

Warning

Experimental! This feature is part of an experimental API preview.

Enums

enum rocfft_status#

rocFFT status/error codes

Values:

enumerator rocfft_status_success#

enumerator rocfft_status_failure#

enumerator rocfft_status_invalid_arg_value#

enumerator rocfft_status_invalid_dimensions#

enumerator rocfft_status_invalid_array_type#

enumerator rocfft_status_invalid_strides#

enumerator rocfft_status_invalid_distance#

enumerator rocfft_status_invalid_offset#

enumerator rocfft_status_invalid_work_buffer#

enum rocfft_transform_type#

Type of transform.

Values:

enumerator rocfft_transform_type_complex_forward#

enumerator rocfft_transform_type_complex_inverse#

enumerator rocfft_transform_type_real_forward#

enumerator rocfft_transform_type_real_inverse#

enum rocfft_precision#

Precision.

Values:

enumerator rocfft_precision_single#

enumerator rocfft_precision_double#

enumerator rocfft_precision_half#

enum rocfft_result_placement#

Result placement.

Declares where the output of the transform should be placed. Note that input buffers may still be overwritten during execution of a transform, even if the transform is not in-place.

Values:

enumerator rocfft_placement_inplace#

enumerator rocfft_placement_notinplace#

enum rocfft_array_type#

Array type.

Values:

enumerator rocfft_array_type_complex_interleaved#

enumerator rocfft_array_type_complex_planar#

enumerator rocfft_array_type_real#

enumerator rocfft_array_type_hermitian_interleaved#

enumerator rocfft_array_type_hermitian_planar#

enumerator rocfft_array_type_unset#

enum rocfft_comm_type#

Communicator type for distributed transforms.

Values:

enumerator rocfft_comm_none#

enumerator rocfft_comm_mpi#

Functions

rocfft_status rocfft_setup()#: Library setup function, called once in program before start of library use.

rocfft_status rocfft_cleanup()#: Library cleanup function, called once in program after end of library use.

rocfft_status rocfft_plan_create(rocfft_plan *plan, rocfft_result_placement placement, rocfft_transform_type transform_type, rocfft_precision precision, size_t dimensions, const size_t *lengths, size_t number_of_transforms, const rocfft_plan_description description)#

Create an FFT plan.

This API creates a plan, which the user can execute subsequently. This function takes many of the fundamental parameters needed to specify a transform.

The dimensions parameter can take a value of 1, 2, or 3. The ‘lengths’ array specifies the size of data in each dimension. Note that lengths[0] is the size of the innermost dimension, lengths[1] is the next higher dimension and so on (column-major ordering).

The ‘number_of_transforms’ parameter specifies how many transforms (of the same kind) needs to be computed. By specifying a value greater than 1, a batch of transforms can be computed with a single API call.

Additionally, a handle to a plan description can be passed for more detailed transforms. For simple transforms, this parameter can be set to NULL.

The plan must be destroyed with a call to rocfft_plan_destroy.

Parameters:

plan – [out] plan handle
placement – [in] placement of result
transform_type – [in] type of transform
precision – [in] precision
dimensions – [in] dimensions
lengths – [in] dimensions-sized array of transform lengths
number_of_transforms – [in] number of transforms
description – [in] description handle created by rocfft_plan_description_create; can be NULL for simple transforms

rocfft_status rocfft_execute(const rocfft_plan plan, void *in_buffer[], void *out_buffer[], rocfft_execution_info info)#

Execute an FFT plan.

This API executes an FFT plan on buffers given by the user.

If the transform is in-place, only the input buffer is needed and the output buffer parameter can be set to NULL. For not in-place transforms, output buffers have to be specified.

Input and output buffers are arrays of pointers. Interleaved array formats are the default, and require just one pointer per input or output buffer. Planar array formats require two pointers per input or output buffer - real and imaginary pointers, in that order.

If fields have been set for transform input or output, these arrays have one pointer per brick in the input or output field, provided in the order that the bricks were added to the field.

Note that input buffers may still be overwritten during execution of a transform, even if the transform is not in-place.

The final parameter in this function is a rocfft_execution_info handle. This optional parameter serves as a way for the user to control execution streams and work buffers.

Parameters:

plan – [in] plan handle
in_buffer – [inout] array (of size 1 for interleaved data, of size 2 for planar data, or one per brick if an input field is set) of input buffers
out_buffer – [inout] array (of size 1 for interleaved data, of size 2 for planar data, or one per brick if an output field is set) of output buffers, ignored for in-place transforms
info – [in] execution info handle created by rocfft_execution_info_create

rocfft_status rocfft_plan_destroy(rocfft_plan plan)#

Destroy an FFT plan.

This API frees the plan after it is no longer needed.

Parameters:: plan – [in] plan handle

rocfft_status rocfft_plan_description_set_scale_factor(rocfft_plan_description description, const double scale_factor)#

Set scaling factor.

rocFFT multiplies each element of the result by the given factor at the end of the transform.

The supplied factor must be a finite number. That is, it must neither be infinity nor NaN.

Parameters:

description – [in] description handle
scale_factor – [in] scaling factor

rocfft_status rocfft_plan_description_set_data_layout(rocfft_plan_description description, const rocfft_array_type in_array_type, const rocfft_array_type out_array_type, const size_t *in_offsets, const size_t *out_offsets, const size_t in_strides_size, const size_t *in_strides, const size_t in_distance, const size_t out_strides_size, const size_t *out_strides, const size_t out_distance)#

Set advanced data layout parameters on a plan description.

This API specifies advanced layout of input/output buffers for a plan description.

The following parameters are supported for inputs and outputs:

Array type (real, hermitian, or complex data, in either interleaved or planar format).
- Real forward transforms require real input and hermitian output.
- Real inverse transforms require hermitian input and real output.
- Complex transforms require complex input and output.
- Hermitian and complex data defaults to interleaved if a specific format is not specified.
Offset of first data element in the data buffer. Defaults to 0 if unspecified.
Stride between consecutive elements in each dimension. Defaults to contiguous data in all dimensions if unspecified.
Distance between consecutive batches. Defaults to contiguous batches if unspecified.

Not all combinations of array types are supported and error codes will be returned for unsupported cases.

Offset, stride, and distance for either input or output provided here is ignored if a field is set for the corresponding input or output.

Parameters:

description – [inout] description handle
in_array_type – [in] array type of input buffer
out_array_type – [in] array type of output buffer
in_offsets – [in] offsets, in element units, to start of data in input buffer
out_offsets – [in] offsets, in element units, to start of data in output buffer
in_strides_size – [in] size of in_strides array (must be equal to transform dimensions)
in_strides – [in] array of strides, in each dimension, of input buffer; if set to null ptr library chooses defaults
in_distance – [in] distance between start of each data instance in input buffer
out_strides_size – [in] size of out_strides array (must be equal to transform dimensions)
out_strides – [in] array of strides, in each dimension, of output buffer; if set to null ptr library chooses defaults
out_distance – [in] distance between start of each data instance in output buffer

rocfft_status rocfft_field_create(rocfft_field *field)#: Create a rocfft field struct.

Warning

Experimental! This feature is part of an experimental API preview.

rocfft_status rocfft_field_destroy(rocfft_field field)#

Destroy a rocfft field struct.

The field struct can be destroyed after being added to the plan description; it is not used for plan execution.

Warning

Experimental! This feature is part of an experimental API preview.

rocfft_status rocfft_get_version_string(char *buf, size_t len)#

Get library version string.

Parameters:

buf – [inout] buffer that receives the version string
len – [in] length of buf, minimum 30 characters

rocfft_status rocfft_plan_description_set_comm(rocfft_plan_description description, rocfft_comm_type comm_type, void *comm_handle)#

Set the communication library for distributed transforms.

Set the multi-processing communication library for a plan.

Multi-processing communication libraries require library-specific handle to also be specified. For MPI libraries, this is a pointer to an MPI communicator.

Parameters:

description – [in] description handle
comm_type – [in] communicator type
comm_handle – [in] handle to communication-library-specific state

rocfft_status rocfft_brick_create(rocfft_brick *brick, const size_t *field_lower, const size_t *field_upper, const size_t *brick_stride, size_t dim, int deviceID)#

Define a brick as part of a decomposition of a field.

Fields can contain a full-dimensional data distribution. The decomposition is specified by providing a lower coordinate and an upper coordinate in the field’s index space. The lower coordinate is inclusive (contained within the brick) and the upper coordinate is exclusive (first index past the end of the brick).

One must also provide a stride for the brick data which specifies how the brick’s data is arranged in memory.

All coordinates and strides include batch dimensions.

A HIP device ID is also provided - each brick may reside on a different device.

All arrays may be re-used or freed immediately after the function returns.

Warning

Experimental! This feature is part of an experimental API preview.

Parameters:

brick – [out] brick structure
field_lower – [in] array of length dim specifying the lower index (inclusive) for the brick in the field’s index space.
field_upper – [in] array of length dim specifying the upper index (exclusive) for the brick in the field’s index space.
brick_stride – [in] array of length dim specifying the brick’s stride in memory
dim – [in] length of brick: includes lengths and batch dimension; must match the dimension of the lengths + batch dimension of the transform.
deviceID – [in] HIP device ID for the device on which the brick’s data is resident.

rocfft_status rocfft_brick_destroy(rocfft_brick brick)#: Deallocate a brick created with rocfft_brick_create.

Warning

Experimental! This feature is part of an experimental API preview.

rocfft_status rocfft_field_add_brick(rocfft_field field, rocfft_brick brick)#

Add a brick to a field.

Note that the order in which the bricks are added is significant; the pointers provided for each brick to rocfft_execute are in the same order that the bricks were added to the field.

The brick may be added to another field or destroyed any time after this function returns.

Warning

Experimental! This feature is part of an experimental API preview.

Parameters:

field – [inout] rocfft_field struct which holds the brick decomposition.
brick – [in] rocfft_brick struct to add to the field.

rocfft_status rocfft_plan_description_add_infield(rocfft_plan_description description, rocfft_field field)#

Add a rocfft_field to a rocfft_plan_description as an input.

The field may be reused or freed immediately after the function returns.

Warning

Experimental! This feature is part of an experimental API preview.

Parameters:

description – [inout] rocfft_plan_description that will pass the field information to plan creation
field – [in] rocfft_field struct added as an input field

rocfft_status rocfft_plan_description_add_outfield(rocfft_plan_description description, rocfft_field field)#

Add a rocfft_field to a rocfft_plan_description as an output.

The field may be reused or freed immediately after the function returns.

Warning

Experimental! This feature is part of an experimental API preview.

Parameters:

description – [inout] rocfft_plan_description that will pass the field information to plan creation
field – [in] rocfft_field struct added as an output field

rocfft_status rocfft_plan_get_work_buffer_size(const rocfft_plan plan, size_t *size_in_bytes)#

Get work buffer size.

Get the work buffer size required for a plan.

Parameters:

plan – [in] plan handle
size_in_bytes – [out] size of needed work buffer in bytes

rocfft_status rocfft_plan_get_print(const rocfft_plan plan)#

Print all plan information.

Prints plan details to stdout, to aid debugging

Parameters:: plan – [in] plan handle

rocfft_status rocfft_plan_description_create(rocfft_plan_description *description)#

Create plan description.

This API creates a plan description with which the user can set extra plan properties. The plan description must be freed with a call to rocfft_plan_description_destroy.

Parameters:: description – [out] plan description handle

rocfft_status rocfft_plan_description_destroy(rocfft_plan_description description)#

Destroy a plan description.

This API frees the plan description. A plan description can be freed any time after it is passed to rocfft_plan_create.

Parameters:: description – [in] plan description handle

rocfft_status rocfft_execution_info_create(rocfft_execution_info *info)#

Create execution info.

This API creates an execution info with which the user can control plan execution and work buffers. The execution info must be freed with a call to rocfft_execution_info_destroy.

Parameters:: info – [out] execution info handle

rocfft_status rocfft_execution_info_destroy(rocfft_execution_info info)#

Destroy an execution info.

This API frees the execution info. An execution info object can be freed any time after it is passed to rocfft_execute.

Parameters:: info – [in] execution info handle

rocfft_status rocfft_execution_info_set_work_buffer(rocfft_execution_info info, void *work_buffer, const size_t size_in_bytes)#

Set work buffer in execution info.

This is one of the execution info functions to specify optional additional information to control execution. This API provides a work buffer for the transform. It must be called before rocfft_execute.

When a non-zero value is obtained from rocfft_plan_get_work_buffer_size, that means the library needs a work buffer to compute the transform. In this case, the user should allocate the work buffer and pass it to the library via this API.

If a work buffer is required for the transform but is not specified using this function, rocfft_execute will automatically allocate the required buffer and free it when execution is finished.

Users should allocate their own work buffers if they need precise control over the lifetimes of those buffers, or if multiple plans need to share the same buffer.

Parameters:

info – [in] execution info handle
work_buffer – [in] work buffer
size_in_bytes – [in] size of work buffer in bytes

rocfft_status rocfft_execution_info_set_stream(rocfft_execution_info info, void *stream)#

Set stream in execution info.

Associates an existing compute stream to a plan. This must be called before the call to rocfft_execute.

Once the association is made, execution of the FFT will run the computation through the specified stream.

The stream must be of type hipStream_t. It is an error to pass the address of a hipStream_t object.

Parameters:

info – [in] execution info handle
stream – [in] underlying compute stream

rocfft_status rocfft_execution_info_set_load_callback(rocfft_execution_info info, void **cb_functions, void **cb_data, size_t shared_mem_bytes)#

Set a load callback for a plan execution (experimental)

This function specifies a user-defined callback function that is run to load input from global memory at the start of the transform. Callbacks are an experimental feature in rocFFT.

Callback function pointers/data are given as arrays, with one function/data pointer per device executing this plan. Currently, plans can only use one device.

The provided function pointers replace any previously-specified load callback for this execution info handle.

Load callbacks have the following signature:

T load_cb(T* data, size_t offset, void* cbdata, void* sharedMem);

‘T’ is the type of a single element of the input buffer. It is the caller’s responsibility to ensure that the function type is appropriate for the plan (for example, a single-precision real-to-complex transform would load single-precision real elements).

A null value for ‘cb’ may be specified to clear any previously registered load callback.

Currently, ‘shared_mem_bytes’ must be 0. Callbacks are not supported on transforms that use planar formats for either input or output.

Parameters:

info – [in] execution info handle
cb_functions – [in] callback function pointers
cb_data – [in] callback function data, passed to the function pointer when it is called
shared_mem_bytes – [in] amount of shared memory to allocate for the callback function to use

rocfft_status rocfft_execution_info_set_store_callback(rocfft_execution_info info, void **cb_functions, void **cb_data, size_t shared_mem_bytes)#

Set a store callback for a plan execution (experimental)

This function specifies a user-defined callback function that is run to store output to global memory at the end of the transform. Callbacks are an experimental feature in rocFFT.

Callback function pointers/data are given as arrays, with one function/data pointer per device executing this plan. Currently, plans can only use one device.

The provided function pointers replace any previously-specified store callback for this execution info handle.

Store callbacks have the following signature:

void store_cb(T* data, size_t offset, T element, void* cbdata, void* sharedMem);

‘T’ is the type of a single element of the output buffer. It is the caller’s responsibility to ensure that the function type is appropriate for the plan (for example, a single-precision real-to-complex transform would store single-precision complex elements).

A null value for ‘cb’ may be specified to clear any previously registered store callback.

Currently, ‘shared_mem_bytes’ must be 0. Callbacks are not supported on transforms that use planar formats for either input or output.

Parameters:

info – [in] execution info handle
cb_functions – [in] callbacks function pointers
cb_data – [in] callback function data, passed to the function pointer when it is called
shared_mem_bytes – [in] amount of shared memory to allocate for the callback function to use

rocfft_status rocfft_cache_serialize(void **buffer, size_t *buffer_len_bytes)#

Serialize compiled kernel cache.

Serialize rocFFT’s cache of compiled kernels into a buffer. This buffer is allocated by rocFFT and must be freed with a call to rocfft_cache_buffer_free. The length of the buffer in bytes is written to ‘buffer_len_bytes’.

rocfft_status rocfft_cache_buffer_free(void *buffer)#

Free cache serialization buffer.

Deallocate a buffer allocated by rocfft_cache_serialize.

rocfft_status rocfft_cache_deserialize(const void *buffer, size_t buffer_len_bytes)#

Deserialize a buffer into the compiled kernel cache.

Kernels in the buffer that match already-cached kernels will replace those kernels that are in the cache. Already-cached kernels that do not match those in the buffer are unmodified by this operation. The cache is unmodified if either a null buffer pointer or a zero length is passed.

file README.md

page index

rocFFT is a software library for computing fast Fourier transforms (FFTs) written in the HIP programming language. It’s part of AMD’s software ecosystem based on ROCm. The rocFFT library can be used with AMD and NVIDIA GPUs.

Documentation#

[!NOTE] The published rocFFT documentation is available at rocFFT in an organized, easy-to-read format, with search and a table of contents. The documentation source files reside in the rocFFT/docs folder of this repository. As with all ROCm projects, the documentation is open source. For more information, see Contribute to ROCm documentation.

To build our documentation locally, use the following code:

cd docs

pip3 install -r sphinx/requirements.txt

python3 -m sphinx -T -E -b html -d _build/doctrees -D language=en . _build/html

Build and install#

You can install rocFFT using pre-built packages or building from source.

Installing pre-built packages:
1. Download the pre-built packages from the ROCm package servers or use the GitHub releases tab to download the source (this may give you a more recent version than the pre-built packages).
2. Run: sudo apt update && sudo apt install rocfft
Building from source:

rocFFT is compiled with AMD’s clang++ and uses CMake. You can specify several options to customize your build. The following commands build a shared library for supported AMD GPUs:
```
mkdir build && cd build
cmake -DCMAKE_CXX_COMPILER=amdclang++ -DCMAKE_C_COMPILER=amdclang ..
make -j
```
You can compile a static library using the -DBUILD_SHARED_LIBS=off option.

With rocFFT, you can use indirect function calls by default; this requires ROCm 4.3 or higher. You can use -DROCFFT_CALLBACKS_ENABLED=off with CMake to prevent these calls on older ROCm compilers. Note that with this configuration, callbacks won’t work correctly.

rocFFT includes the following clients:
- rocfft-bench: Runs general transforms and is useful for performance analysis
- rocfft-test: Runs various regression tests
- Various small samples

Client	CMake option	Dependencies
`rocfft-bench`	`-DBUILD_CLIENTS_BENCH=on`	None
`rocfft-test`	`-DBUILD_CLIENTS_TESTS=on`	Fastest Fourier Transform in the West (FFTW), GoogleTest
samples	`-DBUILD_CLIENTS_SAMPLES=on`	FFTW

Clients are not built by default. To build them, use -DBUILD_CLIENTS=on. The build process downloads and builds GoogleTest and FFTW if they are not already installed.

Clients can be built separately from the main library. For example, you can build all the clients with an existing rocFFT library by invoking CMake from within the rocFFT-src/clients folder:

mkdir build && cd build
cmake -DCMAKE_CXX_COMPILER=amdclang++ -DCMAKE_C_COMPILER=amdclang_PREFIX_PATH=/path/to/rocFFT-lib ..
make -j

To install client dependencies on Ubuntu, run:

bash sudo apt install libgtest-dev libfftw3-dev

We use version 1.11 of GoogleTest.

Examples#

A summary of the latest functionality and workflow to compute an FFT with rocFFT is available on the rocFFT documentation portal.

You can find additional examples in the clients/samples subdirectory.

Support#

You can report bugs and feature requests through the GitHub issue tracker.

Contribute#

If you want to contribute to rocFFT, you must follow our contribution guidelines.

API Reference

Contents

API Reference#

Documentation#

Build and install#

Examples#

Support#

Contribute#