|
|
The Texas Instruments BLAS is an optimized Basic Linear Algebra and Subprogram library for C programmers using TI C66x devices.
The BLAS Documentation provides the documentation and references necessary to integrate BLAS Library routines into a development platform.
The following documentation is available:
| User's Manual | [PDF] |
| Software Manifest | [HTML] |
| Release Notes Archive | [LINK] |
Initial release
This is the first release of this component in this format
| YES | X |
|---|---|
| NO |
| Note: |
|
This release supports the following device families:
This release was built and validated using the following tools:
Questions regarding the BLAS library should be directed to the Texas Instruments TI-RTOS Forum. Please include the text "BLAS" in the title and add "C66x" and "BLAS" tags to your post.
Compatibility keys serve two primary purposes:
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.
| 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. |
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.
| 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 |