2 Using Library Functions

2 Using Library Functions

UsingUsing LibraryLibrary FunctionsFunctions 22 2.1 CALLING FUNCTIONS To use a C library function, simply call the function by name and give the appropriate arguments. The necessary arguments for each function are specified in the Library Reference section of this volume. You can use the librarian, lib21K , described in the ADSP-21000 Family Assembler Tools Manual, to build libraries of your own functions. 2.1.1 Header Files When you use a library function in your program, you should also include the function’s header file (by using the #include directive). The header file for each function is printed at the top of the page of each function’s description in the Library Reference. Header files contain function prototypes. The compiler uses these prototypes to check that each function is called with the correct arguments. 2.1.2 Built-In Functions The C Runtime Library built-in functions are a small set of functions that the compiler immediately recognizes and replaces with in-line assembly code instead of a function call. Typically, in-line assembly code is faster than an average library routine and it does not incur the calling overhead. For example, strcpy() , a function used to copy one string into another space, is recognized by the compiler, which subsequently replaces a call to the C Runtime Library version with an in-line version. Overall, built-in routines are stable and simplistic. The following routines are built-in functions for the G21K compiler: abort() exit() memcmp() abs() strcmp() fabs() strcpy() labs() strlen() memcpy() sqrt() 2 – 1 22 UsingUsing LibraryLibrary FunctionsFunctions If you want to use the C Runtime Library functions of the same name, compile with the -fno-builtin switch. When pointers to pm variables are used, the C Runtime Library functions are used instead of the built-in functions. 2.2 LIBRARY DIRECTORY The linker looks for the runtime library, libc.a , in the sub-directory \21k\lib of the directory specified in the ADI_DSP operating system environment variable. For example, in an MS-DOS system with the value of ADI_DSP set to c:\adi_dsp , the linker looks for the runtime library in the directory c:\adi_dsp\21k\lib . 2.3 LIBRARY SOURCE CODE The source code for the functions and macros in the runtime library is provided on the distribution disks. By default, the installation program copies the source code to a subdirectory of the directory where the runtime libraries are kept, named \21k\lib\src . For example, in the above MS-DOS system the source code for the library is found in the c:\adi_dsp\21k\lib\src directory. Each function is kept in a separate file. The filename is the name of the function with the extension .asm . If you do not intend to modify any of the runtime library functions, you can delete this directory and its contents to conserve disk space. The source code is provided so you can customize any particular function for your own needs. You need proficiency in ADSP-21000 assembly language, and an understanding of the runtime environment, as explained in Chapters 3 and 4 of the ADSP-21000 Family C Tools Manual. It is strongly recommended that you copy the source code to a file with a different filename before you make any modifications to the source code, and that you rename the function itself. Test the function before you use it in your system to verify that it is functionally correct. Note: Analog Devices only supports the runtime library functions as provided. 2 – 2.

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    2 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us