Good to hear. I wasn't able to get very far with latest gcc on AIX 5.3. Since you have made good progress on AIX 6.1, I will not waste any more time on 5.3. That being said, I will try to bootstrap Go library to the latest.
On Monday, 19 December 2016 08:10:56 UTC-8, matthieu.sar...@atos.net wrote: > > I am also working on an AIX port, from another version (GCC 7 on AIX 6.1). > > For now, I have been able to complete the build, but lots of tests are > failing. Some of the changes I made require to be reworked, as I did them > just to allow the build to progress, to have an idea about the amount of > changes required, now I will have to make them work properly. > > I should be able to share my work soon. > > On Friday, December 16, 2016 at 6:46:59 AM UTC+1, scchang wrote: >> >> Not sure if ppl in this thread are still interested. I managed to get >> gccgo (included in gcc 4.8.4) to work on AIX 5.3. The bulk of the changes >> are indeed in the xcoff reader as Ian and others had suggested. xcoff >> writer also has a couple of issues as the default assembler could not >> understand the generated assembly code as it complained about syntax error. >> >> It also appears that IBM were also trying to get gccgo to work on AIX >> based on a recent gcc bug they filed. They probably already got it working. >> Not sure whether and when they would upstream the changes though. >> >> On Thursday, 24 January 2013 14:15:06 UTC-8, minux wrote: >>> >>> >>> On Fri, Jan 25, 2013 at 5:50 AM, Gulácsi Tamás <gth...@gthomas.eu> >>> wrote: >>> >>>> I've stumbled on this: >>>> https://github.com/mirrors/gcc/commit/2c64b281f32d81eafbf0dce8b103ddbf7398ef2f >>>> >>>> What's next? >>>> What shall I do to have Go on AIX? >>>> >>> OK, so simple object reader is completed. If you have some time, you can >>> try >>> building gccgo on AIX and fix build problems as they appear. >>> >>> sorry, i can't provide more details because based on my past experiences, >>> different systems have vastly different problems to solve. You can ask >>> on the >>> mailing list when problem arises. (But please be prepared to upstream >>> your >>> changes if you do want to tackle this) >>> >> -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.