Test flags fall into the following categories, not all of which are
currently supported:

BXX - base flags; items such as -Kieee or -Mfreeform
CXX - compiler flags; items such as -O2 or -Mnoframe
DXX - define flags; items such as -DSPEC or -UMEASURE
IXX - ipa flags; depends on compiler. For PGI, examples include 
      -Mipa=fast or -Mipa=inline
MXX - make flags; items need to be sent to make. An example in the c_correct
      suite is M01, which sets GCCTRI=-trigraphs, needed for test s3 with gcc
NXX - inlining flags; depends on compiler
LXX - linking flags
PXX - profiling flags

Valid flags first need to be entered into the flagdefs database table. A 
chosen flagid is entered, i.e. C00, C01, CH2, etc., followed by the flag1
value. Note that the base flag for each flag type listed above (B00, C00,
etc. for our prepopulated database) has no flag1 value since the base flag
does nothing. Howeve, the C02 entry in the flagdefs table corresponds to
-O2, which is represented in its flag1 column. The flag2 column is not
used currently, but represents more complex cases where multi-pass 
compilation units are used (examples may include, inlinin, IPA, or profile-
guided feedback). Finally, the flag type (b,c,d,i,m.n.l,p) is entered so
that flag entries of the same type can be grouped for processing if needed.
