GLAST/LAT > DAQ and FSW > FSW > Doxygen Index > PBI / V0-0-6

Constituent: test_attribute     Tag: linux-gcc


Interface   Data Structures   File List   Data Fields   Globals  

test_attribute.c File Reference

Unit test of the macros in PBI/Attribute.h. More...

#include <stdio.h>
#include "PBI/Attribute.h"

Include dependency graph for test_attribute.c:

Include dependency graph

Defines

#define YES_OR_NO   "NO"
 Symbol defined to be the string YES or NO depending on wheter the attribute directive is supported.

#define TEST_MISSION
 Symbol representing the string stating the mission of this test. It is purely here to make the code read nicer.


Functions

int main (int argc, char **argv)
 Standard main entry point for Unix platforms. It merely calls the testing routine test_attributes ().

void unused (void) ATTR_UNUSED_OK
 As the name suggests, the unused function used to test the compiler's response to unused static functions.

int test_attribute (void)
 The test program itself and also the entry point for running this test on VxWork's platforms.


Detailed Description

Unit test of the macros in PBI/Attribute.h.

Author:
JJRussell - russell@slac.stanford.edu
   CVS $Id: test_attribute.c,v 1.3 2004/05/06 14:40:25 russell Exp $

This tests whether the compiler supports the __attribute__ directive and, if not, whether PBI/Attribute.h correctly #define's it away.

It directly tests the compiler's warnings on unused static routines. If this code compiled cleanly, then the attribute feature either is supported and works correctly or the attribute feature is not supported, but the compiler does not issue warning message for unused statics.

This is currently the state of affairs with the gcc compiler and the SUN cc compiler. The gcc compiler supports this feature, so no error messages are issued. The SUN cc compiler does not support this feature, but, in turn, does not issue warning messages for unused static routines."

To run the program type


   On Unix platforms: 
   $ test_attribute

   On VxWorks
   > test_attribute ()

 

The program returns 0 if successful, else -1.


Define Documentation

#define TEST_MISSION
 

Value:

"\n"                                                     \
"\n"                                                                          \
" Testing of the Compiler Attributes Directive\n"                             \
" --------------------------------------------\n"                             \
" This tests whether the compiler supports the __attribute__ directive and,\n"\
" if not, whether PBI/Attribute.h correctly #define's it away.\n"             \
"\n"                                                                          \
" It directly tests the compiler's warnings on unused static routines. If\n"  \
" this code compiled cleanly, then the attribute feature either is\n"         \
" supported and works correctly or the attribute feature is not supported,\n" \
" but the compiler does not issue warning message for unused statics.\n"      \
"\n"                                                                          \
" This is currently the state of affairs with the gcc compiler and the SUN\n" \
" cc compiler. The gcc compiler supports this feature, so no error messages\n"\
" are issued. The SUN cc compiler does not support this feature, but, in\n"   \
" turn, does not issue warning messages for unused static routines.\n"
Symbol representing the string stating the mission of this test. It is purely here to make the code read nicer.


Function Documentation

int main int  argc,
char **  argv
 

Standard main entry point for Unix platforms. It merely calls the testing routine test_attributes ().

Return values:
0,if successful
-1,if unsuccessful
This program takes no arguments.

Here is the call graph for this function:

int test_attribute void   ) 
 

The test program itself and also the entry point for running this test on VxWork's platforms.

Return values:
0,if successful
-1,if unsucceful


Generated on Sun Dec 12 07:07:40 2004 by doxygen 1.3.3