HP aC++/HP C A.06.20 Programmer's Guide

LOCALITY
#pragma LOCALITY "string"
string specifies a name to be used for a code section.
The LOCALITY pragma specifies a name to be associated with the code written to a
relocatable object module. The string is forced to be uppercase in C.
All code following the LOCALITY pragma is associated with the name specified in
string. Code that is not headed by a LOCALITY pragma is associated with the name
.text.
The smallest scope of a unique LOCALITY pragma is a function.
For example, the directive,
#pragma LOCALITY "MINE"
builds the name .text.MINE and associates all code following this pragma with this
name, unless another LOCALITY pragma is encountered.
LOCALITY_ALL
#pragma LOCALITY_ALL string
The LOCALITY_ALL pragma specifies a name to be associated with the linker procedures
and global variables that should be grouped together at program binding or load time.
These are written to a relocatable object module. All procedures and global variables
following the LOCALITY_ALL pragma are associated with the name specified in the
string.
VERSIONID
#pragma VERSIONID "string"
string is a string of characters that HP aC++ places in the object file.
The VERSIONID pragma specifies a version string to be associated with a particular
piece of code. The string is placed into the object file produced when the code is
compiled.
For example, the directive
#pragma VERSIONID "Software Product, Version 12345.A.01.05"
places the characters Software Product, Version 12345.A.01.05 into the
object file.
Data Alignment Pragmas
This section discusses the data alignment pragmas and their various arguments available
on HP-UX systems to control alignment across platforms.
Data Alignment Pragmas 127