We have been using SECTALGN(256) with our programs for many years to
ensure they are loaded on a cache line boundary. This causes the
resulting load modules to be page-aligned (and padded to a 4K boundary
which is a waste of storage).
In an effort to trim this waste down, we tried using 'ALIGNT
256,sectname' binder control statements. This was the result for each
named section:
IEW2436W 9517 ESD ALIGNMENTÂ 4096 CONFLICTS WITH USER-SPECIFIED
ALIGNMENT OFÂ 256 FOR SECTION sectname AND CLASS B_TEXT.
The implication is that SECTALGN(256) results in a 4K alignment request
in the ESD even though we specified 256-byte alignment.
What are we doing wrong? How is this supposed to work?
--
Phoenix Software International
Edward E. Jaffe
831 Parkview Drive North
El Segundo, CA 90245
https://www.phoenixsoftware.com/
--------------------------------------------------------------------------------
This e-mail message, including any attachments, appended messages and the
information contained therein, is for the sole use of the intended
recipient(s). If you are not an intended recipient or have otherwise
received this email message in error, any use, dissemination, distribution,
review, storage or copying of this e-mail message and the information
contained therein is strictly prohibited. If you are not an intended
recipient, please contact the sender by reply e-mail and destroy all copies
of this email message and do not otherwise utilize or retain this email
message or any or all of the information contained therein. Although this
email message and any attachments or appended messages are believed to be
free of any virus or other defect that might affect any computer system into
which it is received and opened, it is the responsibility of the recipient
to ensure that it is virus free and no responsibility is accepted by the
sender for any loss or damage arising in any way from its opening or use.
