🚀 go-pugleaf

> 1)Do I need to build gas before building gcc in order to get debugging
> support?

There are really two issues here.  Are you talking about debugging the
compiler, or debugging your gcc compiled programs?  In the former case, you
will definately need to use Utah's pa-gas when building gcc after stage 1.

If you don't use Utah's pa-gas for building gcc, you will have to compile it
WITHOUT the -g option because the native HP assembler doesn't understand the
.stabxxx pseudo-ops.  You will still get a working gcc which is capable of
generating debug output, but you won't be able to debug gcc itself.

In either case, you will need to use Utah's pa-gas in order to use gcc's
debugging info.

> 3)Will gcc-2.3.3 support HP PA with debugging or do I need the version
> of 2.3.1 which is on jaguar (and has been specifically ported for HP
> PA)?  I think building the 2.3.3 release would be better than using
> the 2.1.1 because of bug fixes, etc.

I've been using 2.3.1 from Utah with very few problems.  I haven't tried
2.3.3 yet.

> 3)Once I have gcc-2.x built, do I need to do anything special to build
> pa-gdb-4.6?

Make sure that you install the appropriate patch file from Utah over the
standard GDB-4.6 distribution.  The name is pa-gdb-4.6.tar.Z.  It won't even
compile without that.

> 4)Are there any plans to integrate the utah changes into the
> gas/gcc/gdb standard distributions?

I have been doing a lot of work recently on the PA-GDB port.  It should come
out with release 4.8 of GDB.

			Stu Grossman
			Cygnus Support