all: port to AIX/ppc64

[trex58]

We have started the port of golang v1.10/v1.11 to AIX / ppc64.
It will be available on AIX 7.2 first, maybe on AIX 7.1 too (probably with recent TLs).
Required hardware is Power8 or 9.
64bit only.

Bootstrap with GCC Go 8.1 has been done.
golang tests failures are now being fixed.

Port of golang.org/x has also being started.
First: sys/unix, It will work for both GCC Go and golang on AIX.

We plan to finalize the port in August/September. Available first as RPMs on BullFreeware.

[morya]

Wonderful! Will you guys consider AIX 6.1 ?

[gopherbot]

Change https://golang.org/cl/138115 mentions this issue: go/build, runtime/internal/sys: add GOOS=aix

[trex58]

Wonderful! Will you guys consider AIX 6.1 ?

No. Sorry. AIX 6.1 does not provide all the features required by Go (either GCC Go or golang).

[gopherbot]

Change https://golang.org/cl/138725 mentions this issue: os: add AIX operating system

[gopherbot]

Change https://golang.org/cl/138719 mentions this issue: syscall: change solaris files to libc files

[gopherbot]

Change https://golang.org/cl/138731 mentions this issue: cmd/cgo: add AIX operating system

[gopherbot]

Change https://golang.org/cl/138720 mentions this issue: syscall: add AIX operating system

[gopherbot]

Change https://golang.org/cl/138718 mentions this issue: internal/syscall: add AIX operating system

[gopherbot]

Change https://golang.org/cl/138723 mentions this issue: mime: add AIX operating system

[gopherbot]

Change https://golang.org/cl/138733 mentions this issue: all: change stack layout for AIX

[gopherbot]

Change https://golang.org/cl/138728 mentions this issue: cmd/link: add new loading package for XCOFF files

[gopherbot]

Change https://golang.org/cl/138721 mentions this issue: time: add AIX operating system

[gopherbot]

Change https://golang.org/cl/138716 mentions this issue: runtime: add AIX operating system

[gopherbot]

Change https://golang.org/cl/138717 mentions this issue: internal/poll: add AIX operating system

[gopherbot]

Change https://golang.org/cl/138724 mentions this issue: net: add AIX operating system

[gopherbot]

Change https://golang.org/cl/138722 mentions this issue: crypto: add AIX operating system

[gopherbot]

Change https://golang.org/cl/138727 mentions this issue: debug/xcoff: Add new debug package

[gopherbot]

Change https://golang.org/cl/138730 mentions this issue: cmd/link: add AIX operating system

[gopherbot]

Change https://golang.org/cl/138729 mentions this issue: cmd: add DWARF64 support for aix port

[gopherbot]

Change https://golang.org/cl/138726 mentions this issue: path: add AIX operating system

[gopherbot]

Change https://golang.org/cl/138732 mentions this issue: cmd/go: add AIX operating system

[gopherbot]

Change https://golang.org/cl/138734 mentions this issue: cmd: fix symbols access for AIX

[gopherbot]

Change https://golang.org/cl/138736 mentions this issue: runtime: handle 64bits addresses for AIX

[bcmills]

What should we say about the AIX port in the Go 1.12 release notes?
(CC @andybons)

[trex58]

Hi Bryan,
Clément, who ports golang, is out today and tomorrow. I need to work with him about what we should say about the AIX port of the Go 1.12 release. So, what is the dead-line?

Here is a first list of subjects we'll have to cover I think:

• arch: 64bit only (ppc64)
• processors: Power8 and higher only
• OS version: AIX 7.2 minimum. Better results with TL2 (need to test with TL3 & ASLR)
• Go features not yet supported: cgo, race detector (requires LLVM), pprof, net IPv6, crypto/aes for ppc64, memory sanitizer, more ?
• build-modes not supported: ToBeCompleted
• tests results: ~100% OK in our dev environment. However still some issues on our Go buildfarm VM
• gdb on AIX does not handle perfectly Go yet
• golang.org/x/sys/unix : handles AIX golang (and AIX GCC Go)
• golang.org/x/... : ToBeCompleted
• Performance: ?
• debug/xcoff: ?
• AIX RPMs required for running golang: git, subversion, mercurial, gcc
• AIX RPMs required for building golang: gcc-go ?, patch, coreutils, findutils, file, file-libs, perl, pcre-devel.
• will also be available as AIX RPMs on BullFreeware web-site and then on IBM AIX ToolBox
• other limitations: ?
• other: ?

[bcmills]

That's probably more information than we need for the release notes proper: most of the detail can probably go on an accompanying wiki page (e.g., https://golang.org/wiki/AIX). The release note itself should mostly just make people aware that it's an option.

For some idea of scale, see https://golang.org/doc/go1.11#ports and https://golang.org/doc/go1.8#ports.

[laboger]

Why are you listing crypto/aes as an unsupported feature? I think it should work just like it does for linux/ppc64, it just doesn't have an optimized asm implementation.

…

On Thu, Dec 6, 2018 at 4:26 AM Tony Reix ***@***.***> wrote: Hi Bryan, Clément, who ports golang, is out today and tomorrow. I need to work with him about what we should say about the AIX port of the Go 1.12 release. So, what is the dead-line? Here is a first list of subjects we'll have to cover I think: - arch: 64bit only (ppc64) - processors: Power8 and higher only - OS version: AIX 7.2 minimum. Better results with TL2 (need to test with TL3 & ASLR) - Go features not yet supported: cgo, race detector (requires LLVM), pprof, net IPv6, crypto/aes for ppc64, memory sanitizer, more ? - build-modes not supported: ToBeCompleted - tests results: ~100% OK in our dev environment. However still some issues on our Go buildfarm VM - gdb on AIX does not handle perfectly Go yet - golang.org/x/sys/unix : handles AIX golang (and AIX GCC Go) - golang.org/x/... : ToBeCompleted - Performance: ? - debug/xcoff: ? - AIX RPMs required for running golang: git, subversion, mercurial, gcc - AIX RPMs required for building golang: gcc-go ?, patch, coreutils, findutils, file, file-libs, perl, pcre-devel. - will also be available as AIX RPMs on BullFreeware web-site and then on IBM AIX ToolBox - other limitations: ? - other: ? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#25893 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AI_wjF_SVlc0w0YVOWm6z5IxxGev5I8Bks5u2PDLgaJpZM4UoLak> .

[Helflym]

Hi,

I would said something like that:
"Go is now available on AIX 7.2 on POWER8 architecture (aix/ppc64). External linking, cgo, pprof and race detector aren't yet supported. "

I don't know if you wish to be more precise about buildmode but we can add that only -buildemode=exe is available.

It can also be said that golang.org/x/sys/unix now supports aix/ppc64 on both gc and gccgo.

I think this should be enough. Maybe, I'll add a word about gdb (even if there is an issue about that ?) but it should be available before the true release anyway.

About the Wiki page, that's a good idea ! But does it need to be ready before 1.12 first beta ? Or can I made it after ?

[theonewolf]

@trex58 do we have documented anywhere the limitations preventing getting this off the ground for AIX 6.X?

[pinacoelho]

Wonderful! Will you guys consider AIX 6.1 ?

No. Sorry. AIX 6.1 does not provide all the features required by Go (either GCC Go or golang).

Hi, What's missing in 6.1 ?

[trex58]

@theonewolf @pinacoelho We have to build the complete list of requirements golang has on the AIX operating system.
On AIX 7.2, we see that golang works better (no more test failures) on: 7200-02-02-1810 compared to: 7200-00-02-1614 . See: https://build.golang.org/# ("aix" is on the right) for 7200-02-02-1810 .
Please remember that golang on AIX requires Power8 or 9. Do you have AIX 6.1 on P8 or P9 CECs? We have to check if the last AIX 6.1 TL provides what we need or not, probably no.
We could port golang on AIX 7.1, at least 3 months from now. However, we need to know which TLs do provide golang requirements, and there are other priorities.
What do you plan to do with Go on AIX? Why AIX 6.1?

[theonewolf]

@trex58 I am trying to produce a binary for some old servers that can not be upgraded to AIX 7.X, they are stuck on 6.X.

[trex58]

@trex58 I am trying to produce a binary for some old servers that can not be upgraded to AIX 7.X, they are stuck on 6.X.

golang on AIX, as on Linux/Power, requires Power8 or 9. Are they using such processors with their 6.1 ?
AIX 6.1 is supported on Power8&9 with P7 mode.

[pinacoelho]

1. The AES assembly code does require POWER8 or above, however there is also a pure golang implementation of those functions.
2. AIX 7.1 introduced the openat family of functions. I'm still trying to figure out if golang needs them or just provides an interface to them. (In the later case, their absence isn't critical - in any case, I'm trying to figure out if it's possible to reimplement them in golang)
3. There's still a lot of AIX 6.1 LPARs lying around (namely, the VIOS V2), and a lot of them are excluded from immediate upgrade considerations (for whatever factors). Being able to build golang programs to run on all AIX LPARs (AIX 6.1, 7.1, 7.2 and VIOS V2, V3) would be a great step into bringing them into a DevOps world.

I'm currently in a dead-end situation: AIX 6.1 & 7.1 on POWER5+POWER6, I'm trying to bootstrap gcc/gccgo from the GCC V6, and "it ain't easy" isn't even in the picture yet.
Removing the POWER8&AIX 7.2 requirement would allow me to run the toolset on AIX7.1/POWER6 to build golang into a AIX6.1/POWER5.

Alternate option: build a cross-chain gccgo on linux/x86_64 to aix6.1/ppc64 (power5) to produce an initial golang for aix6.1/power5, but it's looking like a double effort for a half return.

[trex58]

AFAIK, porting golang on AIX 6.1 seems impossible, due to the lack of some DWARF features even in last TLs.
About AIX 7.1, our focus now is AIX 7.2 only (and there are still plenty things to do!).

[owlmind]

I understand it won't work on power7? What is the reason it's power8 or higher only?

[trex58]

@owlmind
We are using a work done by IBM Linux/Power team which started to port golang on Linux/Power for Power8 or higher only: the assembler part, which is common for AIX and Linux/Power. Porting golang on AIX is a very very complex task and we still are improving the quality and we are working hard so that golang 1.12 will be officially available on AIX, including cgo & golang.org/x (March). And we develop on AIX 7.2 on Power8 only today for reducing the complexity. Maybe we'll port golang on AIX 7.1 ; not sure. Maybe that the Power8 requirements can be relaxed ; not sure ; however for now, we haven't yet looked at this. Maybe that P8 assembler code is used only for encryption (which is for now only available for LE platform, thus not for AIX) ; so maybe that being compatible with P7 is not very complex ; however, we may look at these possibilities later, in April probably, when golang works perfectly on AIX 7.2 & P8/9. That depends also on how many AIX users want golang on older environments. Probably that customers wanting to use Go are focused on new applications and are using recent environments (AIX 7.2 & P8/9), which means that porting golang on AIX 7.1 and older HW will not be useful for many AIX users though it will take a lot of work.
Why would you like to have golang on Power7?
Do you want to use existing applications written in Go or do you want to write new applications on AIX due to the qualities of the Go language?
Do you plan to use cgo? (Go -> C or C -> Go ?)

[owlmind]

@trex58 We have a lot of power7 systems and most likely will have to use them for at least 2-3 years. And end of life for AIX 7.1 is 30 April 2022.
We want to use existing applications, particularly filebeat in this case. I was really surprised to see app supported for 7.2 and not for 7.1. Have never seen that before, software on aix usually have pretty good backward compatibility.

[awilfox]

#19074 details the (imo, extremely flimsy) reason that golang does not support POWER7 or lower. There's been some community movement on getting a patchset to support down to POWER5, but it hasn't fully materialised yet. Letting people know just how many of us have non-P8 hardware and want to run Go will help.

[pawel-kedzior-sw]

@trex58 My use-case is to run certain existing utilities written in Go on our customers' environments, which are AIX 7.1 and AIX 7.2. These utilities depend on existing C libraries, so lack of cgo is a blocker.

[Helflym]

@zuraff cgo is now available on master or in RPMs delivered by either us http://www.bullfreeware.com/affichage.php?id=4967 or by IBM on AIXToolBox.
However, it's only available on AIX 7.2, as @trex58 said, 7.1 is not our priority for the moment.

[orz--]

My customers use POWER8, POWER7 for production's environments.
But many cases use POWER7, POWER6 for testing environments.

[awilfox]

I think at this point the only way to get support for stable, older POWER ISAs is GCC Go. The Golang people are not receptive to us, the users of pre-P8 hardware, at all.

[trex58]

I have warned the guys who take decisions about the many people asking for golang on older Power machines with AIX 7.2.

Raw porting on Power7 (and lower maybe) with AIX 7.2 does not seem so complicated. But officially managing older Power versions may be a burden since it requires at first a lot of complementary tasks and it generates then more build/test/maintenance work. It has a cost.

Porting golang on AIX 7.1 seems much more difficult. No plan.

Moreover, now there are also work to be done on GCC Go for GCC v9 (v1.10 to v1.12 : lot of changes) and on golang.org/x (in order to make all golang packages aware of AIX).

The priority for now seems to finalize GCC Go v9 and a complete golang on AIX 7.2 / Power8.
Moreover some very rare issues have to be studied. A quick study of performance must be done too, in order to find the top bottle-necks vs Linux/Power.

Looks like there is an interesting discussion at: #19074 . I need to read it completely.

[ALTree]

@trex58 aix/ppc64 support was merged a while ago; is there anything else that needs to be done here? Or can this issue be closed?

[trex58]

@trex58 aix/ppc64 support was merged a while ago; is there anything else that needs to be done here? Or can this issue be closed?

Yes, it can be closed. It's OK for AIX 7.2 and Power >= 8. About AIX 7.1, we'll see if someone requires it for an important project.

[ALTree]

Nice, thank you. Closing.