User`s guide

Cray XMT™ Programming Environment User’s Guide
The -no_bool compiler switch disables the bool, false and true keywords.
The -no_wchar compiler switch disables the wchar_t keyword. The -cfront
compiler switch disables the bool, explicit, false, true and typename
keywords. The -no_alternative_tokens compiler switch disables the
alternate operator keywords and, and_eq, bitand, bitor, compl, not,
not_eq, or, or_eq, xor, and xor_eq.
In addition to the keywords required by the language standards, the Cray XMT
platform uses several additional reserved words. Most of the additional keywords
reserved by Cray for use on the Cray XMT have two forms: one beginning with an
alphabetic character and one beginning with a double underscore (__). Use the
-no_mta_ext compiler switch to disable Cray XMT keywords beginning with
a letter of the alphabet. However, Cray XMT keywords beginning with a double
underscore are not affected by the -no_mta_ext compiler switch. In addition, the
keywords __int16, __int32, __int64, __short16 and __short32 are
not affected by the -i4 and -short16 compiler switches. For this reason, you
sometimes see the double underscore format in header files to preserve the meaning
of the keywords.
When using the type qualifier keywords to qualify a pointer type, follow the same
rules as for the standard C and C++ type qualifiers. For example, in the following
declaration:
int * sync f;
f is a sync variable of type pointer to int, but in the following declaration:
sync int * f;
f is a pointer to a sync variable of type int.
140 S–2479–20