FIX: MASM Aligns on 4-Byte Boundary After Offset 8000h

Last reviewed: September 11, 1997
Article ID: Q68071
5.10 5.10a | 5.10 5.10a
MS-DOS     | OS/2
kbtool kbfixlist kbbuglist

The information in this article applies to:

  • Microsoft Macro Assembler for MS-DOS, versions 5.1 and 5.1a
  • Microsoft Macro Assembler for OS/2, versions 5.1 and 5.1a

SYMPTOMS

The module below demonstrates a problem with the Microsoft Macro Assembler (MASM) versions 5.1 and 5.1a. If an EVEN directive is used after an offset of 8000h within a segment, the assembler will try to align the next instruction or data element on a 4-byte boundary. In other words, more bytes for padding will be added than are necessary to achieve even alignment.

STATUS

Microsoft has confirmed this to be a problem in MASM versions 5.1 and 5.1a. This problem was corrected in MASM version 6.0.

MORE INFORMATION

The following is the assembly listing that is generated for the example below.

Assembly Listing

Code Generated   Source
--------------   ------

F8               clc
90               EVEN
F8               clc
                 ORG 8000h
F8               clc
87 DB 90         EVEN
F8               clc

Sample Code

; Assemble options needed: none

_TEXT SEGMENT PARA PUBLIC 'CODE' ASSUME CS:_TEXT start:

    clc
    EVEN
    clc
    ORG 8000h
    clc
    EVEN
    clc
_TEXT ENDS

END start


Additional reference words: 5.10 5.10a buglist5.10 buglist5.10a fixlist6.00
KBCategory: kbtool kbfixlist kbbuglist
KBSubCategory: MLIss
Solution Type : kbfix


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: September 11, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.