Pragma Weak_Entry; Function Side-Effect Pragmas - Analog Devices VISUALDSP++ 3.5 Manual

C/c++ compiler and library for adsp-219x processors
Hide thumbs Also See for VISUALDSP++ 3.5:
Table of Contents

Advertisement

C/C++ Compiler Language Extensions
For more information on IPA, see
page
1-57.

#pragma weak_entry

The
#pragma weak_entry
declaration or definition. It applies to the function or variable declaration
or definition that immediately follows the pragma. Use of this pragma
causes the compiler to generate the function or variable definition with
weak linkage.
The following are example uses of the
#pragma weak_entry
int w_var = 0;
#pragma weak_entry
void w_func(){}

Function Side-Effect Pragmas

The function side-effect pragmas are used before a function declaration to
give the compiler additional information about the function in order to
enable it to improve the code surrounding the function call. These prag-
mas should be placed before a function declaration and apply to that
function. For example,
#pragma pure
long dot(short*, short*, int);
The function side-effect pragmas are:
regs_clobbered
1-128
may be used before a static variable or function
, and
result_alignment
VisualDSP++ 3.5 C/C++ Compiler and Library Manual
"Interprocedural Analysis" on
pragma weak_entry
,
,
alloc
pure
const
.
for ADSP-219x DSPs
directive.
,

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the VISUALDSP++ 3.5 and is the answer not in the manual?

Questions and answers

Related Products for Analog Devices VISUALDSP++ 3.5

Table of Contents