Manifest File

Software Name	Version	License Type	Delivered As	Modified by TI
CG_XML	2.61.0	BSD-3-Clause (1)	Source and Binary	N/A	Location	[as_installed]/cg_xml/*
Obtained from	Texas Instruments
XDCTOOLS	3.55.2	EPL-1.0 (1)	Source and Binary	N/A	Location	[as_installed]/xdctools_[version]_core/*
Obtained from	Texas Instruments
TI C6000 Compiler	8.3.2	TI Text AND Thai Open Source Software Center AND BSL-1.0 AND Patrick Powell (1)	Binary	Yes	Location	[as_installed]/ti-cgt-c6000_[version]/bin/*
Obtained from	Texas Instruments, Edison Design Group, http://www.boost.org, http://www.opensource.apple.com/source/distcc/distcc-17/src/snprintf.c
TI C6000 Mklib	8.3.2	BSD-3-Clause (1)	Source and Binary	N/A	Location	[as_installed]/ti-cgt-c6000_[version]/lib/*
Obtained from	Texas Instruments

Software Name	Version	License Type	Delivered As	Modified by TI
Processor SDK RTOS C665x	6.3.0	BSD-3-Clause	Source and Binary	N/A	Location	[as_installed]/processor_sdk_rtos_c665x_[version]/*
Obtained from	Texas Instruments
Posix-SMP Demo	1.1.0	Dhrystone AND BSD-3-Clause	Source and Binary	Yes	Location	[as_installed]/processor_sdk_rtos_c665x_[version]/demos/posix-smp/*
Obtained from	http://fossies.org/linux/privat/old/dhrystone-2.1.tar.gz/
CTOOLSLIB	2.2.0	BSD-3-Clause AND MIT (1)	Source and Binary	N/A	Location	[as_installed]/ctoolslib_[version]/*
Obtained from	Texas Instruments
DSPLIB	3.4.0	BSD-3-Clause (1)	Source and Binary	N/A	Location	[as_installed]/dsplib_c66x_[version]/*
Obtained from	Texas Instruments
EDMA3	2.12.5	BSD-3-Clause (1)	Source and Binary	N/A	Location	[as_installed]/edma3_lld_[version]/*
Obtained from	Texas Instruments
IMGLIB	3.1.1	BSD-3-Clause (1)	Source and Binary	N/A	Location	[as_installed]/imglib_c66x_[version]/*
Obtained from	Texas Instruments
MATHLIB	3.1.2	BSD-3-Clause (1)	Source and Binary	N/A	Location	[as_installed]/mathlib_c66x_[version]/*
Obtained from	Texas Instruments
Framework Components	3.40.2	BSD-3-Clause (1)	Source and Binary	N/A	Location	[as_installed]/framework_components_[version]/*
Obtained from	Texas Instruments
IPC	3.50.4	BSD-3-Clause (1)	Source and Binary	N/A	Location	[as_installed]/ipc_[version]/*
Obtained from	Texas Instruments
NDK	3.61.1	BSD-3-Clause	Source and Binary	N/A	Location	[as_installed]/ndk_[version]/*
Obtained from	Texas Instruments
NS	2.60.1	BSD-3-Clause	Source and Binary	N/A	Location	[as_installed]/ns_[version]/*
Obtained from	Texas Instruments
OpenMP	2.6.3	BSD-3-Clause (1)	Source and Binary	N/A	Location	[as_installed]/openmp_dsp_c665x_[version]/*
Obtained from	Texas Instruments
OpenMP GCC libgomp	4.5.0	GPL-3.0-with-GCC-exception (1)	Source and Binary	Yes	Location	[as_installed]/openmp_dsp_c665x_[version]/packages/ti/runtime/openmp/src/gomp_.
Obtained from	http://gcc.gnu.org/
PDK C665x	2.0.16	BSD-3-Clause	Source and Binary	N/A	Location	[as_installed]/pdk_c665x_[version]/*
Obtained from	Texas Instruments
PDK QM Firmware	2.1.0	TI Text File	Source and Binary	N/A	Location	[as_installed]/pdk_c665x_[version]/packages/ti/drv/qmss/firmware*
Obtained from	Texas Instruments
PDK PCIe Boot Example	1.6.0	GPL-2.0	Source	Yes	Location	[as_installed]/pdk_c665x_[version]/packages/ti/boot/examples/pcie/linux_host_loader/pciedemo.c
Obtained from	Public
PDK RM libfdt	1.3.0	BSD-2-Clause	Source	No	Location	[as_installed]/pdk_c665x_[version]/packages/ti/drv/rm/util/libfdt/*
Obtained from	http://git.jdl.com/gitweb/?p=dtc.git
PDK RM tree.h	1.13	BSD-2-Clause	Source	Yes	Location	[as_installed]/pdk_c665x_[version]/packages/ti/drv/rm/util/tree.h
Obtained from	http://www.openbsd.org/cgibin/cvsweb/src/sys/sys/tree.h
SYS/BIOS	6.76.3	BSD-3-Clause(1)	Source and Binary	N/A	Location	[as_installed]/bios_[version]/*
Obtained from	Texas Instruments
UIA	2.30.1	BSD-3-Clause AND EPL-1.0 (1)	Source and Binary	N/A	Location	[as_installed]/uia_[version]/*
Obtained from	Texas Instruments
XDAIS	7.24.0	BSD-3-Clause(1)	Source and Binary	N/A	Location	[as_installed]/xdais_[version]/*
Obtained from	Texas Instruments
TI C6000 RTS Library	8.3.2	BSD-3-Clause AND Hewlett-Packard AND TI Text AND AFL-3.0 AND MIT AND other similar licenses (1)	Source and Binary	Yes	Location	[as_installed]/ti-cgt-c6000_[version]/include/* and /lib*
Obtained from	Texas Instruments, Hewlett Packard, Edison Design Group, STLport, FreeBSD, OpenBSD
xmodem	N/A	BSD-3-Clause	Source	Yes	Location	[as_installed]/pdk_xx_[version]/packages/ti/board/utils/uartAppLoader/src/xmodem*
Obtained from	http://www.menie.org/georges/embedded/

Licenses

Processor SDK RTOS for C665x Licenses

Processor SDK RTOS C665x, Posix-SMP, PDK C665x, License
-----------------------------------------------------------

Copyright (c) 2015-2018, Texas Instruments Incorporated - http://www.ti.com/
All rights reserved.

Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.

Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the
distribution.

Neither the name of Texas Instruments Incorporated nor the names of
its contributors may be used to endorse or promote products derived
from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

PDK QM Firmware License
------------------------

TEXAS INSTRUMENTS TEXT FILE LICENSE

Copyright (c) 2016 Texas Instruments Incorporated
All rights reserved not granted herein.

Limited License.

Texas Instruments Incorporated grants a world-wide, royalty-free, non-exclusive
license under copyrights and patents it now or hereafter owns or controls to
make, have made, use, import, offer to sell and sell ("Utilize") this software
subject to the terms herein. With respect to the foregoing patent license,
such license is granted solely to the extent that any such patent is necessary
to Utilize the software alone. The patent license shall not apply to any
combinations which include this software, other than combinations with devices
manufactured by or for TI ("TI Devices"). No hardware patent is licensed hereunder.

Redistributions must preserve existing copyright notices and reproduce this license
(including the above copyright notice and the disclaimer and (if applicable) source
code license limitations below) in the documentation and/or other materials provided
with the distribution.

Redistribution and use in binary form, without modification, are permitted provided
that the following conditions are met:
No reverse engineering, decompilation, or disassembly of this software is
permitted with respect to any software provided in binary form.
Any redistribution and use are licensed by TI for use only with TI Devices.
Nothing shall obligate TI to provide you with source code for the software
licensed and provided to you in object code.

If software source code is provided to you, modification and redistribution of the
source code are permitted provided that the following conditions are met:
Any redistribution and use of the source code, including any resulting derivative
works, are licensed by TI for use only with TI Devices.
Any redistribution and use of any object code compiled from the source code
and any resulting derivative works, are licensed by TI for use only with TI Devices.

Neither the name of Texas Instruments Incorporated nor the names of its suppliers
may be used to endorse or promote products derived from this software without
specific prior written permission.

DISCLAIMER.

THIS SOFTWARE IS PROVIDED BY TI AND TI"S LICENSORS "AS IS" AND ANY EXPRESS OR IMPLIED
WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY
AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL TI AND TI"S
LICENSORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE
GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

PDK RM tree.h License
-----------------------

Copyright 2002 Niels Provos
All rights reserved.

Copyright (C) 2013 Texas Instruments Incorporated - http://www.ti.com/
ALL RIGHTS RESERVED

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
1. Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.

THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS"" AND ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

PDK RM libfdt License
----------------------
Note: Libfdt is being used under the BSD License.

Copyright (C) 2006 David Gibson, IBM Corporation.

Redistribution and use in source and binary forms, with or
without modification, are permitted provided that the following
conditions are met:

1. Redistributions of source code must retain the above
copyright notice, this list of conditions and the following
disclaimer.
2. Redistributions in binary form must reproduce the above
copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials
provided with the distribution.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND
CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Dhrystone
-------------------------

Dhrystone Benchmark: Rationale for Version 2 and Measurement Rules

Reinhold P. Weicker
Siemens AG, E STE 35
Postfach 3240
D-8520 Erlangen
Germany (West)

1. Why a Version 2 of Dhrystone?

The Dhrystone benchmark program [1] has become a popular benchmark for
CPU/compiler performance measurement, in particular in the area of
minicomputers, workstations, PC"s and microprocesors. It apparently satisfies
a need for an easy-to-use integer benchmark; it gives a first performance
indication which is more meaningful than MIPS numbers which, in their literal
meaning (million instructions per second), cannot be used across different
instruction sets (e.g. RISC vs. CISC). With the increasing use of the
benchmark, it seems necessary to reconsider the benchmark and to check whether
it can still fulfill this function. Version 2 of Dhrystone is the result of
such a re-evaluation, it has been made for two reasons:

o Dhrystone has been published in Ada [1], and Versions in Ada, Pascal and C
have been distributed by Reinhold Weicker via floppy disk. However, the
version that was used most often for benchmarking has been the version made
by Rick Richardson by another translation from the Ada version into the C
programming language, this has been the version distributed via the UNIX
network Usenet [2].

There is an obvious need for a common C version of Dhrystone, since C is at
present the most popular system programming language for the class of
systems (microcomputers, minicomputers, workstations) where Dhrystone is
used most. There should be, as far as possible, only one C version of
Dhrystone such that results can be compared without restrictions. In the
past, the C versions distributed by Rick Richardson (Version 1.1) and by
Reinhold Weicker had small (though not significant) differences.

Together with the new C version, the Ada and Pascal versions have been
updated as well.

o As far as it is possible without changes to the Dhrystone statistics,
optimizing compilers should be prevented from removing significant
statements. It has turned out in the past that optimizing compilers
suppressed code generation for too many statements (by "dead code removal"
or "dead variable elimination"). This has lead to the danger that
benchmarking results obtained by a naive application of Dhrystone - without
inspection of the code that was generated - could become meaningless.

The overall policiy for version 2 has been that the distribution of
statements, operand types and operand locality described in [1] should remain
unchanged as much as possible. (Very few changes were necessary; their impact
should be negligible.) Also, the order of statements should remain unchanged.
Although I am aware of some critical remarks on the benchmark - I agree with
several of them - and know some suggestions for improvement, I didn"t want to
change the benchmark into something different from what has become known as
"Dhrystone"; the confusion generated by such a change would probably outweight
the benefits. If I were to write a new benchmark program, I wouldn"t give it
the name "Dhrystone" since this denotes the program published in [1].
However, I do recognize the need for a larger number of representative
programs that can be used as benchmarks; users should always be encouraged to
use more than just one benchmark.

The new versions (version 2.1 for C, Pascal and Ada) will be distributed as
widely as possible. (Version 2.1 differs from version 2.0 distributed via the
UNIX Network Usenet in March 1988 only in a few corrections for minor
deficiencies found by users of version 2.0.) Readers who want to use the
benchmark for their own measurements can obtain a copy in machine-readable
form on floppy disk (MS-DOS or XENIX format) from the author.

2. Overall Characteristics of Version 2

In general, version 2 follows - in the parts that are significant for
performance measurement, i.e. within the measurement loop - the published
(Ada) version and the C versions previously distributed. Where the versions
distributed by Rick Richardson [2] and Reinhold Weicker have been different,
it follows the version distributed by Reinhold Weicker. (However, the
differences have been so small that their impact on execution time in all
likelihood has been negligible.) The initialization and UNIX instrumentation
part - which had been omitted in [1] - follows mostly the ideas of Rick
Richardson [2]. However, any changes in the initialization part and in the
printing of the result have no impact on performance measurement since they
are outside the measaurement loop. As a concession to older compilers, names
have been made unique within the first 8 characters for the C version.

The original publication of Dhrystone did not contain any statements for time
measurement since they are necessarily system-dependent. However, it turned
out that it is not enough just to inclose the main procedure of Dhrystone in a
loop and to measure the execution time. If the variables that are computed
are not used somehow, there is the danger that the compiler considers them as
"dead variables" and suppresses code generation for a part of the statements.
Therefore in version 2 all variables of "main" are printed at the end of the
program. This also permits some plausibility control for correct execution of
the benchmark.

At several places in the benchmark, code has been added, but only in branches
that are not executed. The intention is that optimizing compilers should be
prevented from moving code out of the measurement loop, or from removing code
altogether. Statements that are executed have been changed in very few places
only. In these cases, only the role of some operands has been changed, and it
was made sure that the numbers defining the "Dhrystone distribution"
(distribution of statements, operand types and locality) still hold as much as
possible. Except for sophisticated optimizing compilers, execution times for
version 2.1 should be the same as for previous versions.

Because of the self-imposed limitation that the order and distribution of the
executed statements should not be changed, there are still cases where
optimizing compilers may not generate code for some statements. To a certain
degree, this is unavoidable for small synthetic benchmarks. Users of the
benchmark are advised to check code listings whether code is generated for all
statements of Dhrystone.

Contrary to the suggestion in the published paper and its realization in the
versions previously distributed, no attempt has been made to subtract the time
for the measurement loop overhead. (This calculation has proven difficult to
implement in a correct way, and its omission makes the program simpler.)
However, since the loop check is now part of the benchmark, this does have an
impact - though a very minor one - on the distribution statistics which have
been updated for this version.

3. Discussion of Individual Changes

In this section, all changes are described that affect the measurement loop
and that are not just renamings of variables. All remarks refer to the C
version; the other language versions have been updated similarly.

In addition to adding the measurement loop and the printout statements,
changes have been made at the following places:

o In procedure "main", three statements have been added in the non-executed
"then" part of the statement

if (Enum_Loc == Func_1 (Ch_Index, "C"))

they are

strcpy (Str_2_Loc, "DHRYSTONE PROGRAM, 3"RD STRING");
Int_2_Loc = Run_Index;
Int_Glob = Run_Index;

The string assignment prevents movement of the preceding assignment to
Str_2_Loc (5"th statement of "main") out of the measurement loop (This
probably will not happen for the C version, but it did happen with another
language and compiler.) The assignment to Int_2_Loc prevents value
propagation for Int_2_Loc, and the assignment to Int_Glob makes the value of
Int_Glob possibly dependent from the value of Run_Index.

o In the three arithmetic computations at the end of the measurement loop in
"main ", the role of some variables has been exchanged, to prevent the
division from just cancelling out the multiplication as it was in [1]. A
very smart compiler might have recognized this and suppressed code
generation for the division.

o For Proc_2, no code has been changed, but the values of the actual parameter
have changed due to changes in "main".

o In Proc_4, the second assignment has been changed from

Bool_Loc = Bool_Loc | Bool_Glob;

to

Bool_Glob = Bool_Loc | Bool_Glob;

It now assigns a value to a global variable instead of a local variable
(Bool_Loc); Bool_Loc would be a "dead variable" which is not used
afterwards.

o In Func_1, the statement

Ch_1_Glob = Ch_1_Loc;

was added in the non-executed "else" part of the "if" statement, to prevent
the suppression of code generation for the assignment to Ch_1_Loc.

o In Func_2, the second character comparison statement has been changed to

if (Ch_Loc == "R")

("R" instead of "X") because a comparison with "X" is implied in the
preceding "if" statement.

Also in Func_2, the statement

Int_Glob = Int_Loc;

has been added in the non-executed part of the last "if" statement, in order
to prevent Int_Loc from becoming a dead variable.

o In Func_3, a non-executed "else" part has been added to the "if" statement.
While the program would not be incorrect without this "else" part, it is
considered bad programming practice if a function can be left without a
return value.

To compensate for this change, the (non-executed) "else" part in the "if"
statement of Proc_3 was removed.

The distribution statistics have been changed only by the addition of the
measurement loop iteration (1 additional statement, 4 additional local integer
operands) and by the change in Proc_4 (one operand changed from local to
global). The distribution statistics in the comment headers have been updated
accordingly.

4. String Operations

The string operations (string assignment and string comparison) have not been
changed, to keep the program consistent with the original version.

There has been some concern that the string operations are over-represented in
the program, and that execution time is dominated by these operations. This
was true in particular when optimizing compilers removed too much code in the
main part of the program, this should have been mitigated in version 2.

It should be noted that this is a language-dependent issue: Dhrystone was
first published in Ada, and with Ada or Pascal semantics, the time spent in
the string operations is, at least in all implementations known to me,
considerably smaller. In Ada and Pascal, assignment and comparison of strings
are operators defined in the language, and the upper bounds of the strings
occuring in Dhrystone are part of the type information known at compilation
time. The compilers can therefore generate efficient inline code. In C,
string assignemt and comparisons are not part of the language, so the string
operations must be expressed in terms of the C library functions "strcpy" and
"strcmp". (ANSI C allows an implementation to use inline code for these
functions.) In addition to the overhead caused by additional function calls,
these functions are defined for null-terminated strings where the length of
the strings is not known at compilation time; the function has to check every
byte for the termination condition (the null byte).

Obviously, a C library which includes efficiently coded "strcpy" and "strcmp"
functions helps to obtain good Dhrystone results. However, I don"t think that
this is unfair since string functions do occur quite frequently in real
programs (editors, command interpreters, etc.). If the strings functions are
implemented efficiently, this helps real programs as well as benchmark
programs.

I admit that the string comparison in Dhrystone terminates later (after
scanning 20 characters) than most string comparisons in real programs. For
consistency with the original benchmark, I didn"t change the program despite
this weakness.

5. Intended Use of Dhrystone

When Dhrystone is used, the following "ground rules" apply:

o Separate compilation (Ada and C versions)

As mentioned in [1], Dhrystone was written to reflect actual programming
practice in systems programming. The division into several compilation
units (5 in the Ada version, 2 in the C version) is intended, as is the
distribution of inter-module and intra-module subprogram calls. Although on
many systems there will be no difference in execution time to a Dhrystone
version where all compilation units are merged into one file, the rule is
that separate compilation should be used. The intention is that real
programming practice, where programs consist of several independently
compiled units, should be reflected. This also has implies that the
compiler, while compiling one unit, has no information about the use of
variables, register allocation etc. occuring in other compilation units.
Although in real life compilation units will probably be larger, the
intention is that these effects of separate compilation are modeled in
Dhrystone.

A few language systems have post-linkage optimization available (e.g., final
register allocation is performed after linkage). This is a borderline case:
Post-linkage optimization involves additional program preparation time
(although not as much as compilation in one unit) which may prevent its
general use in practical programming. I think that since it defeats the
intentions given above, it should not be used for Dhrystone.

Unfortunately, ISO/ANSI Pascal does not contain language features for
separate compilation. Although most commercial Pascal compilers provide
separate compilation in some way, we cannot use it for Dhrystone since such
a version would not be portable. Therefore, no attempt has been made to
provide a Pascal version with several compilation units.

o No procedure merging

Although Dhrystone contains some very short procedures where execution would
benefit from procedure merging (inlining, macro expansion of procedures),
procedure merging is not to be used. The reason is that the percentage of
procedure and function calls is part of the "Dhrystone distribution" of
statements contained in [1]. This restriction does not hold for the string
functions of the C version since ANSI C allows an implementation to use
inline code for these functions.

o Other optimizations are allowed, but they should be indicated

It is often hard to draw an exact line between "normal code generation" and
"optimization" in compilers: Some compilers perform operations by default
that are invoked in other compilers only when optimization is explicitly
requested. Also, we cannot avoid that in benchmarking people try to achieve
results that look as good as possible. Therefore, optimizations performed
by compilers - other than those listed above - are not forbidden when
Dhrystone execution times are measured. Dhrystone is not intended to be
non-optimizable but is intended to be similarly optimizable as normal
programs. For example, there are several places in Dhrystone where
performance benefits from optimizations like common subexpression
elimination, value propagation etc., but normal programs usually also
benefit from these optimizations. Therefore, no effort was made to
artificially prevent such optimizations. However, measurement reports
should indicate which compiler optimization levels have been used, and
reporting results with different levels of compiler optimization for the
same hardware is encouraged.

o Default results are those without "register" declarations (C version)

When Dhrystone results are quoted without additional qualification, they
should be understood as results obtained without use of the "register"
attribute. Good compilers should be able to make good use of registers even
without explicit register declarations ([3], p. 193).

Of course, for experimental purposes, post-linkage optimization, procedure
merging and/or compilation in one unit can be done to determine their effects.
However, Dhrystone numbers obtained under these conditions should be
explicitly marked as such; "normal" Dhrystone results should be understood as
results obtained following the ground rules listed above.

In any case, for serious performance evaluation, users are advised to ask for
code listings and to check them carefully. In this way, when results for
different systems are compared, the reader can get a feeling how much
performance difference is due to compiler optimization and how much is due to
hardware speed.

6. Acknowledgements

The C version 2.1 of Dhrystone has been developed in cooperation with Rick
Richardson (Tinton Falls, NJ), it incorporates many ideas from the "Version
1.1" distributed previously by him over the UNIX network Usenet. Through his
activity with Usenet, Rick Richardson has made a very valuable contribution to
the dissemination of the benchmark. I also thank Chaim Benedelac (National
Semiconductor), David Ditzel (SUN), Earl Killian and John Mashey (MIPS), Alan
Smith and Rafael Saavedra-Barrera (UC at Berkeley) for their help with
comments on earlier versions of the benchmark.

7. Bibliography

[1]
Reinhold P. Weicker: Dhrystone: A Synthetic Systems Programming Benchmark.
Communications of the ACM 27, 10 (Oct. 1984), 1013-1030

[2]
Rick Richardson: Dhrystone 1.1 Benchmark Summary (and Program Text)
Informal Distribution via "Usenet", Last Version Known to me: Sept. 21,
1987

[3]
Brian W. Kernighan and Dennis M. Ritchie: The C Programming Language.
Prentice-Hall, Englewood Cliffs (NJ) 1978

xModem License
------------------

Copyright 2018 Georges Menie (www.menie.org)
All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:

Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
Neither the name of the University of California, Berkeley nor the
names of its contributors may be used to endorse or promote products
derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS"" AND ANY
EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE REGENTS AND CONTRIBUTORS BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

GPL v2 License
-------------------

GNU GENERAL PUBLIC LICENSE
Version 2, June 1991

Copyright (C) 1989, 1991 Free Software Foundation, Inc.,
51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.

Preamble

The licenses for most software are designed to take away your
freedom to share and change it. By contrast, the GNU General Public
License is intended to guarantee your freedom to share and change free
software--to make sure the software is free for all its users. This
General Public License applies to most of the Free Software
Foundation"s software and to any other program whose authors commit to
using it. (Some other Free Software Foundation software is covered by
the GNU Lesser General Public License instead.) You can apply it to
your programs, too.

When we speak of free software, we are referring to freedom, not
price. Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
this service if you wish), that you receive source code or can get it
if you want it, that you can change the software or use pieces of it
in new free programs; and that you know you can do these things.

To protect your rights, we need to make restrictions that forbid
anyone to deny you these rights or to ask you to surrender the rights.
These restrictions translate to certain responsibilities for you if you
distribute copies of the software, or if you modify it.

For example, if you distribute copies of such a program, whether
gratis or for a fee, you must give the recipients all the rights that
you have. You must make sure that they, too, receive or can get the
source code. And you must show them these terms so they know their
rights.

We protect your rights with two steps: (1) copyright the software, and
(2) offer you this license which gives you legal permission to copy,
distribute and/or modify the software.

Also, for each author"s protection and ours, we want to make certain
that everyone understands that there is no warranty for this free
software. If the software is modified by someone else and passed on, we
want its recipients to know that what they have is not the original, so
that any problems introduced by others will not reflect on the original
authors" reputations.

Finally, any free program is threatened constantly by software
patents. We wish to avoid the danger that redistributors of a free
program will individually obtain patent licenses, in effect making the
program proprietary. To prevent this, we have made it clear that any
patent must be licensed for everyone"s free use or not licensed at all.

The precise terms and conditions for copying, distribution and
modification follow.

GNU GENERAL PUBLIC LICENSE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

0. This License applies to any program or other work which contains
a notice placed by the copyright holder saying it may be distributed
under the terms of this General Public License. The "Program", below,
refers to any such program or work, and a "work based on the Program"
means either the Program or any derivative work under copyright law:
that is to say, a work containing the Program or a portion of it,
either verbatim or with modifications and/or translated into another
language. (Hereinafter, translation is included without limitation in
the term "modification".) Each licensee is addressed as "you".

Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope. The act of
running the Program is not restricted, and the output from the Program
is covered only if its contents constitute a work based on the
Program (independent of having been made by running the Program).
Whether that is true depends on what the Program does.

1. You may copy and distribute verbatim copies of the Program"s
source code as you receive it, in any medium, provided that you
conspicuously and appropriately publish on each copy an appropriate
copyright notice and disclaimer of warranty; keep intact all the
notices that refer to this License and to the absence of any warranty;
and give any other recipients of the Program a copy of this License
along with the Program.

You may charge a fee for the physical act of transferring a copy, and
you may at your option offer warranty protection in exchange for a fee.

2. You may modify your copy or copies of the Program or any portion
of it, thus forming a work based on the Program, and copy and
distribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:

a) You must cause the modified files to carry prominent notices
stating that you changed the files and the date of any change.

b) You must cause any work that you distribute or publish, that in
whole or in part contains or is derived from the Program or any
part thereof, to be licensed as a whole at no charge to all third
parties under the terms of this License.

c) If the modified program normally reads commands interactively
when run, you must cause it, when started running for such
interactive use in the most ordinary way, to print or display an
announcement including an appropriate copyright notice and a
notice that there is no warranty (or else, saying that you provide
a warranty) and that users may redistribute the program under
these conditions, and telling the user how to view a copy of this
License. (Exception: if the Program itself is interactive but
does not normally print such an announcement, your work based on
the Program is not required to print an announcement.)

These requirements apply to the modified work as a whole. If
identifiable sections of that work are not derived from the Program,
and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those
sections when you distribute them as separate works. But when you
distribute the same sections as part of a whole which is a work based
on the Program, the distribution of the whole must be on the terms of
this License, whose permissions for other licensees extend to the
entire whole, and thus to each and every part regardless of who wrote it.

Thus, it is not the intent of this section to claim rights or contest
your rights to work written entirely by you; rather, the intent is to
exercise the right to control the distribution of derivative or
collective works based on the Program.

In addition, mere aggregation of another work not based on the Program
with the Program (or with a work based on the Program) on a volume of
a storage or distribution medium does not bring the other work under
the scope of this License.

3. You may copy and distribute the Program (or a work based on it,
under Section 2) in object code or executable form under the terms of
Sections 1 and 2 above provided that you also do one of the following:

a) Accompany it with the complete corresponding machine-readable
source code, which must be distributed under the terms of Sections
1 and 2 above on a medium customarily used for software interchange; or,

b) Accompany it with a written offer, valid for at least three
years, to give any third party, for a charge no more than your
cost of physically performing source distribution, a complete
machine-readable copy of the corresponding source code, to be
distributed under the terms of Sections 1 and 2 above on a medium
customarily used for software interchange; or,

c) Accompany it with the information you received as to the offer
to distribute corresponding source code. (This alternative is
allowed only for noncommercial distribution and only if you
received the program in object code or executable form with such
an offer, in accord with Subsection b above.)

The source code for a work means the preferred form of the work for
making modifications to it. For an executable work, complete source
code means all the source code for all modules it contains, plus any
associated interface definition files, plus the scripts used to
control compilation and installation of the executable. However, as a
special exception, the source code distributed need not include
anything that is normally distributed (in either source or binary
form) with the major components (compiler, kernel, and so on) of the
operating system on which the executable runs, unless that component
itself accompanies the executable.

If distribution of executable or object code is made by offering
access to copy from a designated place, then offering equivalent
access to copy the source code from the same place counts as
distribution of the source code, even though third parties are not
compelled to copy the source along with the object code.

4. You may not copy, modify, sublicense, or distribute the Program
except as expressly provided under this License. Any attempt
otherwise to copy, modify, sublicense or distribute the Program is
void, and will automatically terminate your rights under this License.
However, parties who have received copies, or rights, from you under
this License will not have their licenses terminated so long as such
parties remain in full compliance.

5. You are not required to accept this License, since you have not
signed it. However, nothing else grants you permission to modify or
distribute the Program or its derivative works. These actions are
prohibited by law if you do not accept this License. Therefore, by
modifying or distributing the Program (or any work based on the
Program), you indicate your acceptance of this License to do so, and
all its terms and conditions for copying, distributing or modifying
the Program or works based on it.

6. Each time you redistribute the Program (or any work based on the
Program), the recipient automatically receives a license from the
original licensor to copy, distribute or modify the Program subject to
these terms and conditions. You may not impose any further
restrictions on the recipients" exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties to
this License.

7. If, as a consequence of a court judgment or allegation of patent
infringement or for any other reason (not limited to patent issues),
conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License. If you cannot
distribute so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you
may not distribute the Program at all. For example, if a patent
license would not permit royalty-free redistribution of the Program by
all those who receive copies directly or indirectly through you, then
the only way you could satisfy both it and this License would be to
refrain entirely from distribution of the Program.

If any portion of this section is held invalid or unenforceable under
any particular circumstance, the balance of the section is intended to
apply and the section as a whole is intended to apply in other
circumstances.

It is not the purpose of this section to induce you to infringe any
patents or other property right claims or to contest validity of any
such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system, which is
implemented by public license practices. Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing
to distribute software through any other system and a licensee cannot
impose that choice.

This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.

8. If the distribution and/or use of the Program is restricted in
certain countries either by patents or by copyrighted interfaces, the
original copyright holder who places the Program under this License
may add an explicit geographical distribution limitation excluding
those countries, so that distribution is permitted only in or among
countries not thus excluded. In such case, this License incorporates
the limitation as if written in the body of this License.

9. The Free Software Foundation may publish revised and/or new versions
of the General Public License from time to time. Such new versions will
be similar in spirit to the present version, but may differ in detail to
address new problems or concerns.

Each version is given a distinguishing version number. If the Program
specifies a version number of this License which applies to it and "any
later version", you have the option of following the terms and conditions
either of that version or of any later version published by the Free
Software Foundation. If the Program does not specify a version number of
this License, you may choose any version ever published by the Free Software
Foundation.

10. If you wish to incorporate parts of the Program into other free
programs whose distribution conditions are different, write to the author
to ask for permission. For software which is copyrighted by the Free
Software Foundation, write to the Free Software Foundation; we sometimes
make exceptions for this. Our decision will be guided by the two goals
of preserving the free status of all derivatives of our free software and
of promoting the sharing and reuse of software generally.

NO WARRANTY

11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
REPAIR OR CORRECTION.

12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.

END OF TERMS AND CONDITIONS

How to Apply These Terms to Your New Programs

If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.

To do so, attach the following notices to the program. It is safest
to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least
the "copyright" line and a pointer to where the full notice is found.

Copyright (C)

This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.

You should have received a copy of the GNU General Public License along
with this program; if not, write to the Free Software Foundation, Inc.,
51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.

Also add information on how to contact you by electronic and paper mail.

If the program is interactive, make it output a short notice like this
when it starts in an interactive mode:

Gnomovision version 69, Copyright (C) year name of author
Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w".
This is free software, and you are welcome to redistribute it
under certain conditions; type `show c" for details.

The hypothetical commands `show w" and `show c" should show the appropriate
parts of the General Public License. Of course, the commands you use may
be called something other than `show w" and `show c"; they could even be
mouse-clicks or menu items--whatever suits your program.

You should also get your employer (if you work as a programmer) or your
school, if any, to sign a "copyright disclaimer" for the program, if
necessary. Here is a sample; alter the names:

Yoyodyne, Inc., hereby disclaims all copyright interest in the program
`Gnomovision" (which makes passes at compilers) written by James Hacker.

, 1 April 1989
Ty Coon, President of Vice

This General Public License does not permit incorporating your program into
proprietary programs. If your program is a subroutine library, you may
consider it more useful to permit linking proprietary applications with the
library. If this is what you want to do, use the GNU Lesser General
Public License instead of this License.

Processor SDK RTOS for C665x Manifest

2020-23-03

Manifest ID - SRAS00007071

Legend

Disclaimers

Export Control Classification Number (ECCN)

Links in the Manifest

Open Source License References

Export Information

Processor SDK RTOS for C665x Development Host Content

Processor SDK RTOS for C665x Target Device Content

Credits

Licenses

Processor SDK RTOS for C665x Licenses

Software Name	The name of the application or file
Version	Version of the application or file
License Type	Type of license(s) under which TI will be providing software to the licensee (e.g. BSD-3-Clause, GPL-2.0, TI TSPA License, TI Commercial License). The license could be under Commercial terms or Open Source. See Open Source Reference License Disclaimer in the Disclaimers Section. Whenever possible, TI will use an SPDX Short Identifier for an Open Source License. TI Commercial license terms are not usually included in the manifest and are conveyed through a variety of means such as a clickwrap license upon install, a signed license agreement and so forth.
Location	The directory name and path on the media or a specific file where the Software is located. Typically fully qualified path names are not used and instead the relevant top level directory of the application is given. A notation often used in the manifests is [as installed]/directory/. Note that the asterisk implies that all files under that directory are licensed as the License Type field denotes. Any exceptions to this will generally be denoted as [as installed]/directory/ except as noted below which means as shown in subsequent rows of the manifest.
Delivered As	This field will either be “Source”, “Binary” or “Source and Binary” and is the primary form the content of the Software is delivered in. If the Software is delivered in an archive format, this field applies to the contents of the archive. If the word Limited is used with Source, as in “Limited Source” or “Limited Source and Binary” then only portions of the Source for the application are provided.
Modified by TI	This field will either be “Yes” or “No”. A “Yes” means TI has made changes to the Software. A “No” means TI has not made any changes. Note: This field is not applicable for Software “Obtained from” TI.
Obtained from	This field specifies from where or from whom TI obtained the Software. It may be a URL to an Open Source site, a 3^rd party licensor, or TI. See Links Disclaimer in the Disclaimers Section.