Re: GNU gcc/g++ with 386 segmented architecture.

paik@3dfx.com
1 Jul 1996 10:16:27 -0400

          From comp.compilers
Related articles
GNU gcc/g++ with 386 segmented architecture. mgcd@QSof01.alcbel.be (1996-06-24)
Re: GNU gcc/g++ with 386 segmented architecture. kanze@lts.sel.alcatel.de (1996-06-24)
Re: GNU gcc/g++ with 386 segmented architecture. dennis@netcom.com (1996-06-26)
Re: GNU gcc/g++ with 386 segmented architecture. khays@sequent.com (1996-06-26)
Re: GNU gcc/g++ with 386 segmented architecture. bill.williams@gecm.com (1996-06-27)
Re: GNU gcc/g++ with 386 segmented architecture. dlmoore@ix.netcom.com (1996-06-30)
Re: GNU gcc/g++ with 386 segmented architecture. paik@3dfx.com (1996-07-01)
Re: GNU gcc/g++ with 386 segmented architecture. dlmoore@ix.netcom.com (1996-07-01)
Re: GNU gcc/g++ with 386 segmented architecture. brian@watcom.on.ca (1996-07-01)
Re: GNU gcc/g++ with 386 segmented architecture. sef@kithrup.com (Sean Eric Fagan) (1996-07-01)
| List of all articles for this month |
From: paik@3dfx.com
Newsgroups: comp.compilers
Date: 1 Jul 1996 10:16:27 -0400
Organization: 3Dfx Interactive
References: 96-06-100
Keywords: 386, performance, C

[John: C compiler that did 386 large model]


[Dave: Watcom V10.5 claims it does them]


I've used far pointers in Watcom 10.5. They work, but while I
haven't gone and disassembled the generated code, they seem to
be very slow. Some code we have here which interfaces to some
hardware runs at about 1/2 performance when the hardware is
mapped through far pointers instead of near.


Sam Paik
--
        Samuel S. Paik / paik@3dfx.com / 415-919-2441 / I speak only for myself


--

Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.