delorie.com/archives/browse.cgi | search |
Xref: | news-dnh.mv.net comp.os.msdos.djgpp:4171 |
Path: | news-dnh.mv.net!mv!news.sprintlink.net!newsfeed.internetmci.com!in1.uu.net!rice!news!sandmann |
From: | Charles Sandmann <sandmann AT clio DOT rice DOT edu> |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Re: DJASM |
Date: | Sun, 07 Jan 1996 13:03:58 CST |
Organization: | Rice University, Houston, Texas |
Lines: | 9 |
Message-ID: | <30f0191e.sandmann@clio.rice.edu> |
References: | <4coqpn$11tu AT bird3 DOT i-link DOT net> |
Reply-To: | sandmann AT clio DOT rice DOT edu |
NNTP-Posting-Host: | clio.rice.edu |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
> DJASM: I may be wrong but this appears to be an AT&T assembly > compiler for DJGPP. Am I wrong? Is there any documentation? Its actually an intel-like syntax, not AT&T. It's a 16-bit assembler which knows about 32-bit opcodes, handles a single source file and builds an EXE file directly (no .obj) or a binary fragment (for inclusion in other code). Used for writing the stub for V2, and some other applications in development. It allows everything needed to build DJGPP apps to be distributed freely (unlike GO32, which required TCC or BCC to build).
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |