public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Doug Evans <devans@cygnus.com>
To: dave@nic.com
Cc: linux-gcc@vger.rutgers.edu, egcs@cygnus.com
Subject: Re: pgcc and gcc question
Date: Fri, 17 Oct 1997 12:53:00 -0000	[thread overview]
Message-ID: <199710171842.LAA01655@charmed.cygnus.com.> (raw)
In-Reply-To: <Pine.GSO.3.95q.971017112726.1906A-100000@nic.com>

   Date: 	Fri, 17 Oct 1997 11:29:19 -0400 (EDT)
   From: Dave Wreski <dave@nic.com>

   Hi all.  I mailed the maintainers of the pentium gcc compiler, but never
   got a response.  I'm hoping someone can help me here.

   I'm starting to hear more and more about pgcc vs gcc, and wondered which I
   should be using.

   Why haven't these pentium optimizations been included in the normal gcc
   compiler?

   If they are so great, I would think they would be included in the normal
   gcc release..

I would suggest asking this question in egcs@cygnus.com.
[So I've cc'd them ...]

           reply	other threads:[~1997-10-17 12:53 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <Pine.GSO.3.95q.971017112726.1906A-100000@nic.com>]

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=199710171842.LAA01655@charmed.cygnus.com. \
    --to=devans@cygnus.com \
    --cc=dave@nic.com \
    --cc=egcs@cygnus.com \
    --cc=linux-gcc@vger.rutgers.edu \
    /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).