From: "M. R. Brown" <mrbrown@0xd6.org>
To: Angel Lacal <angel@nmp.es>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PGCC and other optimized compilers...
Date: Thu, 11 Oct 2001 14:29:47 -0500 [thread overview]
Message-ID: <20011011142947.A590@0xd6.org> (raw)
In-Reply-To: <3BC5CCBF.11326FB8@nmp.es>
In-Reply-To: <3BC5CCBF.11326FB8@nmp.es>
* Angel Lacal <angel@nmp.es> on Thu, Oct 11, 2001:
> You (and the others) are telling pgcc is a buggy compiler, or at least
> not as confiable as gcc... ?is that true?
AFAIK the pgcc is no longer being maintained, since the pgcc optimizations
have long since been folded into (egcs) gcc.
M. R.
prev parent reply other threads:[~2001-10-11 19:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-11 16:45 Angel Lacal
2001-10-11 19:29 ` M. R. Brown [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=20011011142947.A590@0xd6.org \
--to=mrbrown@0xd6.org \
--cc=angel@nmp.es \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®