Path: g2news1.google.com!news3.google.com!feeder2.cambriumusenet.nl!feeder1.cambriumusenet.nl!feed.tweaknews.nl!194.134.4.91.MISMATCH!news2.euro.net!feeds.phibee-telecom.net!cmeerw.net!www.openwatcom.org!not-for-mail
From: "Peter C. Chapin" <PCha...@vtc.vsc.edu>
Newsgroups: openwatcom.users.fortran
Subject: Re: 64 bit hardware
Date: Fri, 10 Dec 2010 20:09:39 -0500
Organization: Vermont Technical College
Lines: 14
Message-ID: <iduj1e$5p9$1@www.openwatcom.org>
References: <idu3r2$jot$1@www.openwatcom.org> <idu7ek$nvu$1@www.openwatcom.org>
NNTP-Posting-Host: 184.53.80.138
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Trace: www.openwatcom.org 1292029808 5929 184.53.80.138 (11 Dec 2010 01:10:08 GMT)
X-Complaints-To: news@www.openwatcom.org
NNTP-Posting-Date: Sat, 11 Dec 2010 01:10:08 +0000 (UTC)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
In-Reply-To: <idu7ek$nvu$1@www.openwatcom.org>

On 2010-12-10 16:52, Hans-Bernhard Bröker wrote:

> 32-bit code doesn't generally pay any significant speed penalty unless
> you intend to use exorbitantly large quantities of something.

I should add that if you are using a 64 bit operating system, you can't
run the 16 bit programs generated by Open Watcom (or any other 16 bit
programs for that matter). At least this is definitely true for 64 bit
Windows 7.

Of course this only matters if you want to develop for 16 bit targets
(and intend to test your code on your development station).

Peter