Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!usc!jarthur!nntp-server.caltech.edu!schmke
From: schmke@nntp-server.caltech.edu (Kevin Todd Schmidt)
Newsgroups: comp.lang.c
Subject: Re: C compiler for 386 or 486
Message-ID: <1991Apr29.204405.8649@nntp-server.caltech.edu>
Date: 29 Apr 91 20:44:05 GMT
References: <2498@pdxgate.UUCP> <1991Apr29.141040.4271@ux1.cso.uiuc.edu> <2518@pdxgate.UUCP>
Organization: California Institute of Technology, Pasadena
Lines: 31

In article <2518@pdxgate.UUCP> mwizard@eecs.cs.pdx.edu (Craig Nelson) writes:
>gordon@osiris.cso.uiuc.edu (John Gordon) writes:
>
>>mwizard@eecs.cs.pdx.edu (Craig Nelson) writes:
>
>>>Bob.Stout@p6.f506.n106.z1.fidonet.org (Bob Stout) writes:
>
>>>>Zortech C/C++ has code generation switches to generate both 386 and 486 
>>>>specific code. 
>
>>>So does TCC/TCC++
>
>>	It does?  I thought that Turbo C only had switches to do 8088 or
>>186/286 code.
>
>	Really. When in doubt, you can always ask a Borland rep :) , but
>I generate the code by first compiling command line with the -c -S options,
>then use the /3 or .386 options with tasm.exe when recompiling the asm code.
>Works for me ...

But the asm code you are assembling is still only 8088/8086 code and
doesn't contain any 386/486 specific instructions so what are you gaining?
Nothing really!!!

______________________________________________________________________________
        _  ____   _  |                           |
       / // _  \ / / | Kevin T. Schmidt          | schmke@gap.cco.caltech.edu
      / // /_/ // /  | Jet Propulsion Laboratory |
 _   / // ____// /   | 4800 Oak Grove Dr.        |
/ /_/ // /    / /___ | M/S 301-355               |
\____//_/    /_____/ | Pasadena, CA  91109       |