Implementation defined behavior control
Implementation defined behavior is controlled by
Lprefix (if any) , the outer quotes, and leading/trailing whitespace from string-literal, replaces each
\, then tokenizes the result (as in translation stage 3), and then uses the result as if the input to
Pragma directive controls implementation-specific behavior of the compiler, such as disabling compiler warnings or changing alignment requirements. Any pragma that is not recognized is ignored.
 Non-standard pragmas
The ISO C++ language standard does not require the compilers to support any pragmas. However, several non-standard pragmas are supported by multiple implementations:
 #pragma STDC
ISO C language standard requires that C compilers support the following three pragmas, and some C++ compiler vendors support them, to varying degrees, in their C++ frontends:
where arg is either
ON, informs the compiler that the program will access or modify floating-point environment, which means that optimizations that could subvert flag tests and mode changes (e.g., global common subexpression elimination, code motion, and constant folding) are prohibited. The default value is implementation-defined, usually
), and |x+iy| = √x2
, despite the possibility of intermediate overflow. In other words, the programmer guarantees that the range of the values that will be passed to those function is limited. The default value is
The behavior of the program is undefined if any of the three pragmas above appear in any context other than outside all external declarations or preceding all explicit declarations and statements inside a compound statement.
Note: compilers that do not support these pragmas may provide equivalent compile-time options, such as gcc's
 #pragma once
#pragma once is a non-standard pragma that is supported by the vast majority of modern compilers. If it appears in a header file, it indicates that it is only to be parsed once, even if it is (directly or indirectly) included multiple times in the same source file.
Standard approach to preventing multiple inclusion of the same header is by using include guards:
#ifndef LIBRARY_FILENAME_H #define LIBRARY_FILENAME_H // contents of the header #endif /* LIBRARY_FILENAME_H */
So that all but the first inclusion of the header in any translation unit are excluded from compilation. All modern compilers record the fact that a header file uses an include guard and do not re-parse the file if it is encountered again, as long as the guard is still defined. (see e.g. gcc)
With #pragma once, the same header appears as
#pragma once // contents of the header
Unlike header guards, this pragma makes it impossible to erroneously use the same macro name in more than one file. On the other hand, since with #pragma once files are excluded based on their filesystem-level identity, this can't protect against including a header twice if it exists in more than one location in a project.
 #pragma pack
This family of pragmas control the maximum alignment for subsequently defined class and union members.
where arg is a small power of two and specifies the new alignment in bytes.
#pragma pack may decrease the alignment of a class, however, it cannot make a class overaligned.
|This section is incomplete|
Reason: Explain the effects of this pragmas on data members and also the pros and cons of using them. Sources for reference:
|This section is incomplete|
Reason: no example
- C++ pragmas in Visual Studio 2019
- Pragmas accepted by GCC
- Individual pragma descriptions and Standard pragmas in IBM AIX XL C 16.1
- Appendix B. Pragmas in Sun Studio 11 C++ User's Guide
- Intel C++ compiler pragmas
- Release nodes (includes pragmas) for HP aCC A.06.25
 See also
C documentation for Implementation defined behavior control