FFTLIB 2.0.1.3 Release Notes

---

Contents

1. Introduction
2. Getting Started
3. Documentation
4. What's New
5. Upgrade and Compatibility Information
6. Device Support
7. Validation Information
8. Known Issues
9. Technical Support
10. Component Release Notes

---

Introduction

The FFTLIB is an optimized library for computing the discrete Fourier transform (DFT).

• Supports K2H TI DSP platform for little-endian
• Supports single-precision and double-precision floating point
• Supports complex inputs and real inputs
• Supports 1D, 2D and 3D FFT
• Supports Single-core and Multi-core
• API similar to FFTW, includes FFT plan and FFT execute

---

Getting Started

The FFTLIB User's Manual provides the documentation and references necessary to integrate FFTLIB Library routines into a development platform.

---

Documentation

The following documentation is available:

User's Manual	[HTML]
Software Manifest	[HTML]
Release Notes Archive	[LINK]

---

What's New

The following new features were added:

1. Linux Build support

The following bugs have been resolved:

1. 106689 Provide FFT Benchmarking on Slayton
2. 106910 Multicore overheads with FFTLib (with OpenMP)
3. 107667 makefiles don't work on Linux, and include prebuilt Library
4. 108168 Application still needs to include header files inside src/common/
5. 108180 Warnings while including FFTLIB header files
6. 108184 FFT benchmarking need include offload overhead and provide comparison result of DSP

---

Upgrade and Compatibility Information

This version of FFTLIB is compatible with the last released version:

YES	X
NO

Note:

Package compatibility keys are independent of component release versions. For more information visit: Package Versioning and Compatibility

---

Device Support

This release supports the following device families:

• k2hx DSP (ELF, Little-Endian format)

---

Validation Information

This release was built and validated using the following tools:

• XDC Tools version: null
• RTSC Packaging Standard version: 2.0
• C6000 Code Generation Tools version: null
• Code Composer Studio version: ll
• GNU make version: 3.81

---

Known Issues

1. N/A

---

Technical Support

Questions regarding the FFTLIB library should be directed to the MCSDK HPC forum. Please include the text "FFTLIB" in the title and add "k2hx" and "FFTLIB" tags to your post.

---

Component Release Notes

1. FFTLIB Release Notes

---

---

Package Versioning and Compatibility

Compatibility Keys

Compatibility keys serve two primary purposes:

1. Enable tooling to identify incompatibilities between components
2. Convey a level of compatibility between different releases to set end user expectations.

Each compatibility key is composed of 4 comma-delimited numbers - represented here by the letters M, S, R and P [M,S,R,P]. The table below provides a descriptive reference for compatibility key intention.

Compatibility Key Reference

Key	Meaning	Description
1 (M=Major)	Break in compatibility	The package consumer is required to re-write the calling source code to use the package
2 (S=Source)	Source compatibility	The package consumer�s source code doesn't require change, but does require a recompile
3 (R=Radix)	Introduction of new features	Compatibility with previous interfaces is not broken. If libraries are provided by the package, an application must re-link with the new libraries, but is not required to recompile its source
4 (P=Patch)	Bug fixes only	If libraries are provided by the package, an application must re-link with the new libraries, but is not required to recompile its source.

---

Versioning

Each package version is composed of 4 period-delimited numbers - represented here by the letters M, m, p and b [M.m.p.b]. The table below provides a descriptive reference regarding package version numbering.

Package Version Reference

Digit	Meaning	Description
1 (M=Major)	Major revision	Incremented when the new version is substantially different from the previous For example, a new module added or an existing module's algorithm significantly altered.
2 (m=minor)	Minor revision	Incremented when the new version has changed but not in a major way. For example, some minor changes in the API or feature set.
3 (p=patch)	Patch number	Incremented for all other source code changes. This include any packaging support code.
4 (b=build)	Build number	Incremented for each release delivery to CM. Reset for any change to M, m or p