Re: Correct goarch.sh settings for gccgo on hppa?

[matoro <matoro_mailinglist_kernel@matoro.tk>]

Oh sorry, should have clarified.  I did all those parts already, just 
didn't include them because I assumed the at-fault piece would be in 
goarch.sh.  This is for Linux only.

All I did for the conditional stuff was add HPPA to all the 32-bit 
files, and add the two unique syscall numbers.  This was based on the 
instructions in configure.ac.  Here is the complete patch:  
https://dpaste.com/HVHNU9BKF.txt

Is there something I might be missing?

-------- Original Message --------
Subject: Re: Correct goarch.sh settings for gccgo on hppa?
Date: 2022-11-26 00:25
 From: Ian Lance Taylor <iant@golang.org>
To: matoro <matoro_mailinglist_kernel@matoro.tk>

On Fri, Nov 25, 2022 at 8:31 PM matoro
<matoro_mailinglist_kernel@matoro.tk> wrote:
> 
> Thank you both for the suggestions.  I tried the following values:
> 
> diff --git a/libgo/goarch.sh b/libgo/goarch.sh
> index 977f318b3..e0d6a3ad8 100755
> --- a/libgo/goarch.sh
> +++ b/libgo/goarch.sh
> @@ -88,6 +88,16 @@ case $goarch in
>                  ;;
>          esac
>          ;;
> +    hppa)
> +       bigendian=true
> +       defaultphyspagesize=4096
> +       family=HPPA
> +       int64align=8
> +       minframesize=64
> +       pcquantum=4
> +       ptrsize=4
> +       stackalign=64
> +       ;;
>       ia64)
>          family=IA64
>          cachelinesize=128
> 
> But unfortunately got the same result.  I wonder if there is something
> else missing?
> 
> Ian, if you have the time, I have a machine you can use to look at 
> this.

As far as I know gccgo has never been ported to parisc.  This requires
a fair bit more than just fixing up goarch.sh.  There are a bunch of
files in libgo that are conditionally compiled based on the GOARCH
(processor) and GOOS (operating system) values.  These are marked in
the files by comments that start with "+build" or "go:build".  Many of
those comments will need to be adjusted to recognize parisc and
whatever operating system you are using.  If this is for HP/UX, there
is also operating specific code required in various places.

I'm happy to answer questions about doing the port, but it's not a 
trivial task.

Ian