From: Marc Espie <espie@quatramaran.ens.fr>
To: rjschwei@mindspring.com
Cc: gcc@gcc.gnu.org
Subject: Re: configure flag request
Date: Fri, 28 Jul 2000 06:20:00 -0000 [thread overview]
Message-ID: <200007281320.PAA10195@quatramaran.ens.fr> (raw)
In-Reply-To: <397E61AA.D3B69F66@mindspring.com>
Such machines are broken.
You may get away with it on specific occasions.
Don't count on it.
I certainly hope that things will get worse, specifically, that
gcc optimizations will get better, and the compiler will produce
faster code.... all with a chance that your L2 cache won't catch
up if it's broken.
You're looking in the wrong place. Complain to the PC's manufacturer.
prev parent reply other threads:[~2000-07-28 6:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-25 20:57 Robert Schweikert
2000-07-28 6:20 ` Marc Espie [this message]
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=200007281320.PAA10195@quatramaran.ens.fr \
--to=espie@quatramaran.ens.fr \
--cc=gcc@gcc.gnu.org \
--cc=rjschwei@mindspring.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).