Looks like Jim beat me to the punch, so I'll only add a few comments.

Jim Winstead Jr. (jwinstea@fenris.claremont.edu) wrote:
: In article <1992Aug14.040459.29047@cs.ucf.edu> hab@engr.ucf.edu (Hubert Bahr) writes:
: >Not when HJ only provides GCC only as a binary using jump tables for
: >it.  We are forced to use at least GCC with jump tables.
: 
: Ahem.  prep.ai.mit.edu:/pub/gnu/gcc-2.2.2.tar.Z, and
: banjo.concert.net:/pub/Linux/GCC/gcc-2.2.2.tar.Z will give you the
: most current source for GCC.  If you're that ocncenred with not using
: jump-table libs, compile it yourself.  :)

In the latest test release (soon to be the latest public release),
both normal and jump table shared binaries use the *same* shared image
so they can happily coexist on a single system without wasting disk
space because of multiple images.  If you don't want the stuff you
compile to use the jump tables, don't link with the "-jump" option.
If that's not good enough for you, then do as Jim says and compile GCC
yourself

: >I for one want to know that I have an up to date source library for all
: >the software I use.  I also want this library compilable with the current
: >make files and utilities.  Yes it will take extensive work to automate
: >this recompile effort, but I think the dividends are multifold, 1st If
: 
: Um, I'm glad you have the diskspace to keep the source around, and the
: time to recompile everything.  Most of us don't.

Same here, I'd rather spend my time on more productive ventures.

: >I check things when they have just been changed, the changers will probably
: >be more responsive to bug reports.  2  New versions of GCC and libraries
: >are usually to fix bugs or performance flaws.  How can I take advantage
: >of those changes without recompiling anyway.  3.  I can take advantage
: 
: Most GCC/libc releases are to fix bugs in libc - with jump table
: libraries, just copy the new library into place and *all* binaries
: linked against the jump table libraries use the new routines.  No
: recompilation necessary.

I can only think one compiler problem we've had since v2.2.2 and it
was due to a library bug.  Just think, GCC itself could have been
fixed automatically had it been using jump tables libs at the time.

David
-- 
David Engel                        Optical Data Systems, Inc.
david@ods.com                      1101 E. Arapaho Road
(214) 234-6400                     Richardson, TX  75081