Mail Archives: pgcc/1999/03/13/15:59:08
On Sat, Mar 13, 1999 at 12:16:20PM -0500, Jonathan Mark Brooks wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
> Just out of curiosity, will we see 3DNow! optimizations in the pgcc
> compiler?
If AMD gives me a dual amd-k7 machine, yes.
> Also, my understanding is that the next revision of ecgs is supposed
> to incorporate the pgcc x86 specific optimizations.
No. the process of enhancing egcs to pgccs level is gradual. Its not a
question of just applying the patch to egcs, its a continual re-engineerig
process to adapt the pgcc changes to the egcs environment.
Egcs has two goals that currently conflict with pgcc:
- must be rock-solid on x86 AND on other architectures. I'm working on
making pgcc run on other archs, though, so this might go away.
- the compiler mustn's use ages to compile a program. pgcc often trades
a large increase in compile time for relatively small code improvements.
This is not acceptable for egcs, so the algorithms have to be improved.
> I saw the thread but I wasn't sure why this is a problem with 2.2 kernels,
> i.e., why you can't use the ecgs or pgcc compilers without error.
You can use pgcc-1.1.1, actually. you can also *usually* use the
snapshots. I just don't want to hear any bug reports, as I'm tired of
debugging the kernel.
See the egcs faq (http://egcs.cygnus.com/), what it says about the kernel
also applies to pgcc, with he added limitation that I don't want to see
ugly bug reports, and my desire for seeing "pgcc is broken, it can't
compile linux" is growing towards negative infinity.
--
-----==- |
----==-- _ |
---==---(_)__ __ ____ __ Marc Lehmann +--
--==---/ / _ \/ // /\ \/ / pcg AT goof DOT com |e|
-=====/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+
The choice of a GNU generation |
|
- Raw text -