[Bug go/84484] libgo configure tests fail to find -latomic

2018-02-22 Thread ian at airs dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84484 Ian Lance Taylor changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug go/84484] libgo configure tests fail to find -latomic

2018-02-22 Thread ian at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84484 --- Comment #17 from ian at gcc dot gnu.org --- Author: ian Date: Thu Feb 22 19:49:04 2018 New Revision: 257914 URL: https://gcc.gnu.org/viewcvs?rev=257914=gcc=rev Log: PR go/84484 libgo: add support for riscv64 Patch by

[Bug go/84484] libgo configure tests fail to find -latomic

2018-02-21 Thread sch...@linux-m68k.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84484 --- Comment #16 from Andreas Schwab --- Created attachment 43484 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=43484=edit libgo support for riscv64 With this patch I can sucessfully build libgo for riscv64.

[Bug go/84484] libgo configure tests fail to find -latomic

2018-02-21 Thread ian at airs dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84484 --- Comment #15 from Ian Lance Taylor --- > The first hunk is useless since this is a compile test. Understood, but I would prefer to test the exact options that the build is going to use.

[Bug go/84484] libgo configure tests fail to find -latomic

2018-02-21 Thread sch...@linux-m68k.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84484 --- Comment #14 from Andreas Schwab --- See gcc/config/riscv/linux.h for why it does that.

[Bug go/84484] libgo configure tests fail to find -latomic

2018-02-21 Thread sch...@linux-m68k.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84484 --- Comment #13 from Andreas Schwab --- The first hunk is useless since this is a compile test.

[Bug go/84484] libgo configure tests fail to find -latomic

2018-02-21 Thread ian at airs dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84484 --- Comment #12 from Ian Lance Taylor --- How about this patch? diff --git a/libgo/configure b/libgo/configure index aba4dc39..dcfc524b 100755 --- a/libgo/configure +++ b/libgo/configure @@ -14209,7 +14209,7 @@ if test

[Bug go/84484] libgo configure tests fail to find -latomic

2018-02-21 Thread sch...@linux-m68k.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84484 --- Comment #11 from Andreas Schwab --- See comment #0.

[Bug go/84484] libgo configure tests fail to find -latomic

2018-02-21 Thread ian at airs dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84484 --- Comment #10 from Ian Lance Taylor --- In what way does it fail? The final link of libgo is always done against ../libatomic/libatomic.la.

[Bug go/84484] libgo configure tests fail to find -latomic

2018-02-21 Thread sch...@linux-m68k.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84484 --- Comment #9 from Andreas Schwab --- That does not work because CFLAGS gets reset after the test. Only PTHREAD_CFLAGS survives.

[Bug go/84484] libgo configure tests fail to find -latomic

2018-02-20 Thread wilson at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84484 Jim Wilson changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug go/84484] libgo configure tests fail to find -latomic

2018-02-20 Thread ian at airs dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84484 --- Comment #8 from Ian Lance Taylor --- Odd. In any case, the patch is simple: diff --git a/libgo/configure b/libgo/configure index aba4dc39..1b61c9ba 100755 --- a/libgo/configure +++ b/libgo/configure @@ -14210,6 +14210,9 @@ if test

[Bug go/84484] libgo configure tests fail to find -latomic

2018-02-20 Thread sch...@linux-m68k.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84484 --- Comment #7 from Andreas Schwab --- The patch file link.

[Bug go/84484] libgo configure tests fail to find -latomic

2018-02-20 Thread ian at airs dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84484 --- Comment #6 from Ian Lance Taylor --- Give me a hint: what doesn't work?

[Bug go/84484] libgo configure tests fail to find -latomic

2018-02-20 Thread sch...@linux-m68k.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84484 --- Comment #5 from Andreas Schwab --- That doesn't work.

[Bug go/84484] libgo configure tests fail to find -latomic

2018-02-20 Thread ian at airs dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84484 --- Comment #4 from Ian Lance Taylor --- To get the change from https://golang.org/cl/95436 in the form of a patch, click on the download link (middle of the screen on the right) then click on one of the "patch file" links at the bottom of the

[Bug go/84484] libgo configure tests fail to find -latomic

2018-02-20 Thread sch...@linux-m68k.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84484 --- Comment #3 from Andreas Schwab --- https://golang.org/cl/95436 doesn't contain any patch.

[Bug go/84484] libgo configure tests fail to find -latomic

2018-02-20 Thread sch...@linux-m68k.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84484 --- Comment #2 from Andreas Schwab --- contains a preliminary patch to add support for riscv, you also need

[Bug go/84484] libgo configure tests fail to find -latomic

2018-02-20 Thread ian at airs dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84484 --- Comment #1 from Ian Lance Taylor --- Does the patch in https://golang.org/cl/95436 fix the problem? Note that there will be other problems building libgo for riscv: it will need to be added to goarch.sh, match.sh, and testsuite/gotest, and