From: "Andrew Crabtree" Newsgroups: comp.os.msdos.djgpp Subject: Re: AT&T 2 Intel ASM converter Date: Tue, 17 Feb 1998 09:28:27 -0800 Organization: Hewlett Packard Lines: 28 Message-ID: <6cchbi$khs$1@rosenews.rose.hp.com> References: <34E5F1AC DOT 97AA9F67 AT worldonline DOT nl> NNTP-Posting-Host: ros51675cra.rose.hp.com Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Precedence: bulk Reinier Heeres wrote in message <34E5F1AC DOT 97AA9F67 AT worldonline DOT nl>... >-I don't know how to handle the .def's exactly Don't worry about .defs. Those are coff debug info. NASM doesn't support them (yet). If it does it will probably use the same syntax as gas (i hope). >-I don't know how to handle the .comm's exactly NASM does have a comm directive. It is still lacking an lcomm equivalent though. From the help ... The COMMON directive is used to declare common variables. A common variable is much like a global variable declared in the uninitialised data section, so that common intvar 4 is similar in function to global intvar section .bss intvar resd 1