Mail Archives: djgpp/1997/09/17/05:00:38
On 17 Sep 97 07:22:41 GMT, Herman Schoenfeld said:
> >: ... There are no MSVC compilers for them so any comment comparing
> >: GCC to MSVC is pretty much a waste of bandwidth.
> >
> >Wrong. Some of us can read assembly language files generated by
> >compilers. Some of us can link modules from "foreign" compilers that
> >don't natively target a particular environment.
>
> No, it's not "wrong". MSVC doesn't support linux. Why must you fill this
> newgroup with your lies?
My understanding is that MSVC's object format is a well documented,
publically known format called "COM" which is not specifically tied to
the Windows operating system. What this means is that you can take code
compiled from C/C++ into .OBJ files, and if you've crafted your own
linker, you can splice them together for whatever OS you want on the x86
so long as it supports 32 bit FLAT mode programming.
> >: DJGPP does support pentium optimising. (PGCC).
> >
> >Misleading. The patched compiler sometimes (not often) produces code that
> >is slower than the original 486 optimizer's code.
More to the point, I believe this compiler can generate code which is
incorrect (that was the status last I checked).
> Wait 6months-1year and DJGPP will fully support pentium optimizations along
> with a myriad of other features making it ideal choice for game programmers.
You've got to be kidding. Who's going to put their project on hold for 6
months just so that they can wait for a compiler to catch up to a chip
that will be obsolete? When will djgpp have P-II optimizations?
> (ie, full support for windows, full support for directx (if not already))
That would be impressive, considering Microsoft is not going to support
them in any way. That's not to say its impossible (reverse engineering
can go a long way) but even WATCOM needed inside information and
cooperation from Microsoft to get Direct X working with their compiler.
--
Paul Hsieh
http://www.geocities.com/SiliconValley/9498/mailme.html
- Raw text -