Message-ID: <993ABB8870CED011BF1F00A0C95B7F0AE631F9@nt17pv.apsc.com>
From: "Webb, James R(V97187)" <JRWEBB AT apsc DOT com>
To: "'pgcc AT delorie DOT com'" <pgcc AT delorie DOT com>
Subject: RE: gcc-2.7.0 creates faster code than pgcc-1.1.1
Date: Thu, 11 Mar 1999 07:19:55 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2232.9)
Content-Type: text/plain
Reply-To: pgcc AT delorie DOT com

FWIW, I've been using pgcc-1.1.1 on the 2.1/2.2 kernel releases without any
observed problems.

----------
From: 	hpj DOT lisa AT t-online DOT de[SMTP:hpj DOT lisa AT t-online DOT de]
Sent: 	Wednesday, March 10, 1999 7:12 PM
To: 	pgcc AT delorie DOT com
Subject: 	Re: gcc-2.7.0 creates faster code than pgcc-1.1.1

Marc Lehmann wrote:
>  
> > > This is with the snapshot pgcc, btw. The release might have some
> > > hand-tuning to be correct rather than fast in some cases.
> >
> > Because of some probs with current pgcc mentioned in linux-kernel and
> 
> (btw, the linux-kernel is not fixed to work with newer versions of gcc,
> so you better not try that one. Also, kde only recently upgraded their
> sources to C++ (they used an unsupported c++ dialect before that pgcc does
> not understand)).

The only problems, I had (with pgcc 1.1.1), was some mega functions in
kspread,
which is in alpha stage anyway. Currently the CVS HEAD branch is a mess, b/c
they move the whole stuff to qt 2.0, so this is inedible for me. Even
koffice
in the 1.1 branch doesn't compile for me :( not depending on what cc is
used...

What I care is the significant bigger binaries with pgcc (although I use it
as long as it compiles). Is it because the alignments, or bigger obcodes
used?
I'm interested in your recommendation of options to get the smallest
possible 
code (beside -Os)?

> > kde-devel, I restrained from installing egcs/pgcc snapshot versions.
> 
> I'm very picky about these issues. AFAIK there are problems with both kde
> and linux-kernel, NOT with egcs or pgcc.
> 
> (Surely pgcc snapshots have bugs, but people just like to claim "egcs" is
> broken. They will be surprised when the next gcc version won't compile
> their programs, either)

I had a few problems with macros without parentheses... No big deal.
 
> > When the next release is planned? What about Linus' whining about
> > undefined references and inlining? Is there a consence now?
> 
> The consensus is that Linus tries to read the documentation before
> flaming and the egcs developers try to help the kernel by supporting more
> interfaces in the future.
> 
> Also, Linus does not support current gcc, egcs or pgcc. Point.

Sometimes, something has to show him, he's mortal, too ;)
 
> > Do you think, that current snapshots optimizes k6 objects really better,
> > or is there any other explanation about our experiences?
> 
> The snapshots have a totally different (and IMHO better) scheduling
> system for amd. I haven't benchmarked these extensivley (not at all, to
> be clear), but they might indeed make a few percent difference. When in
> doubt, run your favourite benchmark/application. The latter test will tell
> you wether pgcc is _really_ faster for _your_ problem.

Kernelwise, i will stick to 2.7.2.3 then, but I will try cvs-pgcc on the
rest
and let you you. What cc do you use for your kernel?

> --
>       -----==-                                             |
>       ----==-- _                                           |
>       ---==---(_)__  __ ____  __       Marc Lehmann      +--
>       --==---/ / _ \/ // /\ \/ /       pcg AT goof DOT com      |e|
>       -=====/_/_//_/\_,_/ /_/\_\       XX11-RIPE         --+
>     The choice of a GNU generation                       |
>                                                          |