For functions declared with the naked attribute, the compiler generates code without prolog and epilog code. You can use this feature to write your own prolog/epilog code sequences using inline assembler code. Naked functions are particularly useful in writing virtual device drivers.
Because the naked attribute is only relevant to the definition of a function and is not a type modifier, naked functions use the extended attribute syntax, described previously. For example, this code defines a function with the naked attribute:
__declspec( naked ) int func( formal_parameters )
{
// Function body
}
Or, alternatively:
#define Naked __declspec( naked )
Naked int func( formal_parameters )
{
// Function body
}
The naked attribute affects only the nature of the compiler’s code generation for the function’s prolog and epilog sequences. It does not affect the code that is generated for calling such functions. Thus, the naked attribute is not considered part of the function’s type, and function pointers cannot have the naked attribute. Furthermore, the naked attribute cannot be applied to a data definition. For example, this code sample generates an error:
__declspec( naked ) int i; // Error--naked attribute not
// permitted on data declarations.
The naked attribute is relevant only to the definition of the function and cannot be specified in the function’s prototype. For example, this declaration generates a compiler error:
__declspec( naked ) int func(); // Error--naked attribute not
// permitted on function declarations