MATHLIB 3.1.2.4 Release Notes

---

Contents

1. Introduction
2. Getting Started
3. Mathlib RTS
4. Documentation
   
5. What's New
   
6. Fixed Bugs
   
7. Upgrade and Compatibility Information
   
8. Device Support
   
9. Validation Information
   
   
10. Rebuilding MATHLIB
    
11. Known Issues
    
12. Technical Support
    
13. Package Versioning and Compatability
    
    

---

Introduction

The MATHLIB bundle comprises the Floating-Point Math Function Library package together with the software tools (SWTOOLS) package in bundle format to simplify the release procedure.

---

Getting Started

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

---

Mathlib RTS

The Mathlib RTS package provides symbol names same as in standard RTS library. They can be used to replace standard RTS library function call.

---

Documentation

The following documentation is available:

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

---

What's New

• MATHLIB test report including benchmarking is based on C6000 Compiler 8.3.2.
• MATHLIB compilation and build is now part of Proc-SDK build process.
• TIREX .json metadata is included in the package. It enables CCS v7 and newer to detect and install MATHLIB without going through pop-up installation window and restarting CCS. The installation folder path is
  COM_TI_MAS_MATHLIB_<target>_INSTALL_DIR, where target is C674X or C66X.

---

Fixed Bugs

• PRSDK-4876: Atan2dp crashes when one of the input variable is zero

---

Upgrade and Compatibility Information

This version of MATHLIB 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:

• C674x DSP (ELF, Little-Endian format)

---

Validation Information

This release was built and validated using the following tools:

• XDC Tools version: 3.51.01.18
• RTSC Packaging Standard version: 2.0
• C6000 Code Generation Tools version: 8.3.2
• Code Composer Studio version: 8.1

---

Rebuilding MATHLIB

To rebuild MATHLIB, clone the git repo at https://git.ti.com/ep-processor-libraries/mathlib and follow build instructions in readme.txt in root folder.

---

Known Issues

• C66 assembly implementation of Mathlib kernels is not available in this release. The assembly version of each kernel is exactly the same as the C version. Please ignore the profiling results for assembly version.
• Kernels acossp, asinsp, atanhdp and atanhsp are not included in the Mathlib RTS build, since C6000 RTS has faster implementation than Mathlib for these kernels.

---

Technical Support

Questions regarding the MATHLIB library should be directed to one of the following forums based on the device that this library is used for:

• E2E Support Forums for AM335x, AM437x, and AM57xx
• E2E Support Forums for K2H, K2K, K2E, K2L, K2G, C665x, and C667x
• E2E Support Forums for OMAP-L13x and C674x

Please include the text "MATHLIB" in the title and add "C674x" or "C66x" tags to your post.

---

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