MATHLIB 3.1.2.1 Release Notes

May 17, 2016

MATHLIB Bundle Release Notes


Contents

  1. Introduction
  2. Getting Started
  3. Mathlib RTS
  4. Documentation
  5. What's New
  6. Upgrade and Compatibility Information
  7. Device Support
  8. Validation Information
  9. MISRA Compliance
  10. Known Issues
  11. Technical Support
  12. 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]
[CHM]
Test Report [HTML]
Software Manifest [HTML]
Release Notes Archive [LINK]
MISRA Compliance Documentation[LINK]


What's New

MISRA-C 2004 compliance has been added to the c66x release of MATHLIB

The following requirements have been met:

The following bugs have been resolved:


Upgrade and Compatibility Information

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

YES X
NO

Note:
  1. 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:


Validation Information

This release was built and validated using the following tools:


MISRA Compliance

The c66x release complies with MISRA standards as detailed in the [Compliance Document]


Known Issues


Technical Support

Questions regarding the MATHLIB library should be directed to corresponding device forums:


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


Copyright 2016, Texas Instruments Incorporated