* Matthew Parker writes to All, on Tuesday November 19 1996
   at 12:51:

 MP>  I noticed the following error using watcom 10.6 and I was interested
 MP> in knowing if anyone knows if its a known bug and been fixed. Also if
 MP> its in earlier versions or not.

Does it actually cause any problems?

 MP> int1c_:         push    ax
 MP>                 push    cx
 MP>                 push    dx
 MP>                 push    bx
 MP>                 push    sp
 MP>                 push    bp
 MP>                 push    si
 MP>                 push    di
 MP>                 push    ds
 MP>                 push    es
 MP>                 push    ax
 MP>                 push    ax
 MP>                 mov     bp,sp
 MP>                 cld
 MP>                 mov     ax,seg L2
 MP>                 mov     ds,ax
 MP>                 pop     ax
 MP>                 pop     ax
 MP>                 pop     es
 MP>                 pop     ds
 MP>                 pop     di
 MP>                 pop     si
 MP>                 pop     bp
 MP>                 pop     bx  ;should be pop sp
 MP>                 pop     bx
 MP>                 pop     dx
 MP>                 pop     cx
 MP>                 pop     ax
 MP>                 iret

I see 12 pushes and 12 pops, so SP will have the same value on exit as it
did on entry. BX will also be set correctly; the first pop sets it to the
pushed value of SP, then the second pop the pushed value of BX.

The order of pushes matches exactly that of the 186+ opcode PUSHA; POPA
also discards SP, same as the above code.

I don't see any problems with the above code at all ... it appears to
correctly emulate PUSHA and POPA.

Cheers.

---