public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Dessent <brian@dessent.net>
To: cygwin@cygwin.com
Subject: Re: Cygwin on Windows Me on Athlon64
Date: Fri, 26 Sep 2003 23:25:00 -0000	[thread overview]
Message-ID: <3F74CA8C.75EE2CC5@dessent.net> (raw)
In-Reply-To: <000b01c38484$98929a80$0300a8c0@o8k4x4>

Koide wrote:
> 
> Now I am using cygwin on Windows Me on AthlonXP .
> 
>  I will have Athlon64 system shortly . Then I want to use cygwin
> on Athlon64 . The executable files of programs comliled on Athlon64
> should be much faster than those are compiled on AthlonXP .
> 
>  Then now I am wondering if ;
> 1 . Can cygwin be installed correctly on Windows Me on Athlon64 .
>     (Just the same as using the install wizard .)
> 2 . To compile the program , gcc is certainly needed .
>     To compile the program of 64bit , is it sufficient to install
>     gcc using the install wizard and type "gcc ______.c" ?

I would be very surpised if Windows ME supported any kind of 64 bit
extensions.  You most likely will need to wait for the 64 bit version of
Windows XP to be released to take full advantage.  However, the Athlon
64 will be much faster simply because it is highly optimized for 32 bit
stuff, that's the whole point.  You can have your cake and eat it too:
old stuff runs fast, and when support eventually makes it into the OS,
compiler, and software, then you get an additional increase.

Brian

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

  reply	other threads:[~2003-09-26 23:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-26 23:21 Koide
2003-09-26 23:25 ` Brian Dessent [this message]
2003-09-27 14:33 ` Tim Prince

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3F74CA8C.75EE2CC5@dessent.net \
    --to=brian@dessent.net \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).