[Bug go/79037] gccgo: Binaries crash with parforsetup: pos is not aligned on m68k

2017-02-01 Thread ian at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79037 --- Comment #14 from ian at gcc dot gnu.org --- Author: ian Date: Wed Feb 1 23:35:59 2017 New Revision: 245110 URL: https://gcc.gnu.org/viewcvs?rev=245110=gcc=rev Log: PR go/79037 Backport from mainline: compiler, runtime:

[Bug go/79037] gccgo: Binaries crash with parforsetup: pos is not aligned on m68k

2017-01-23 Thread ian at airs dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79037 Ian Lance Taylor changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug go/79037] gccgo: Binaries crash with parforsetup: pos is not aligned on m68k

2017-01-23 Thread ian at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79037 --- Comment #12 from ian at gcc dot gnu.org --- Author: ian Date: Mon Jan 23 18:15:22 2017 New Revision: 244824 URL: https://gcc.gnu.org/viewcvs?rev=244824=gcc=rev Log: PR go/79037 compiler, runtime: align gc data for m68k The

[Bug go/79037] gccgo: Binaries crash with parforsetup: pos is not aligned on m68k

2017-01-21 Thread glaubitz at physik dot fu-berlin.de
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79037 --- Comment #11 from John Paul Adrian Glaubitz --- Testing the latest patchset from Gerrit [1], I can confirm the bug is now fixed: (sid-m68k-sbuild)root@jessie64:~# cat hello-world.go package main import "fmt" func main() {

[Bug go/79037] gccgo: Binaries crash with parforsetup: pos is not aligned on m68k

2017-01-20 Thread gcc-bugzilla at mkarcher dot dialup.fu-berlin.de
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79037 --- Comment #10 from Michael Karcher --- OK, I got it. I retract my last comment.

[Bug go/79037] gccgo: Binaries crash with parforsetup: pos is not aligned on m68k

2017-01-20 Thread ian at airs dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79037 --- Comment #9 from Ian Lance Taylor --- The backend.h interface says that if you set the alignment, that is the alignment. I could change it to the GCC version--you can only increase the alignment--but I'd rather keep the backend.h interface

[Bug go/79037] gccgo: Binaries crash with parforsetup: pos is not aligned on m68k

2017-01-19 Thread gcc-bugzilla at mkarcher dot dialup.fu-berlin.de
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79037 --- Comment #8 from Michael Karcher --- The patch looks like it should work fine, I guess John Paul Adrian Glaubitz is going to test it soon. But I wonder whether the determination of alignment is in types.cc really needed, as user-specified

[Bug go/79037] gccgo: Binaries crash with parforsetup: pos is not aligned on m68k

2017-01-19 Thread ian at airs dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79037 --- Comment #7 from Ian Lance Taylor --- Can someone with m68k hardware please test the patch at https://golang.org/cl/35478? Thanks. (To download just the patch as a zip file:

[Bug go/79037] gccgo: Binaries crash with parforsetup: pos is not aligned on m68k

2017-01-19 Thread ian at airs dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79037 --- Comment #6 from Ian Lance Taylor --- I don't think it's the type descriptors that need to be aligned, I think it's just the GC symbol pointers. Those are the ones whose names end in "$gc" in the list above.

[Bug go/79037] gccgo: Binaries crash with parforsetup: pos is not aligned on m68k

2017-01-18 Thread gcc-bugzilla at mkarcher dot dialup.fu-berlin.de
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79037 --- Comment #5 from Michael Karcher --- The root issue now is that the ABI gcc implements on m68k is incompatible with the Go runtime shipped with gcc. The Go runtime uses the lowest two bits in the type information pointer as flags (called

[Bug go/79037] gccgo: Binaries crash with parforsetup: pos is not aligned on m68k

2017-01-18 Thread glaubitz at physik dot fu-berlin.de
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79037 --- Comment #4 from John Paul Adrian Glaubitz --- Disabling the Go garbage collector fixes this particular crash: (sid-m68k-sbuild)root@jessie64:~# GOGC=off ./hello-world Hello World! (sid-m68k-sbuild)root@jessie64:~# So it seems GOGC is not

[Bug go/79037] gccgo: Binaries crash with parforsetup: pos is not aligned on m68k

2017-01-16 Thread glaubitz at physik dot fu-berlin.de
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79037 --- Comment #3 from John Paul Adrian Glaubitz --- (In reply to John Paul Adrian Glaubitz from comment #2) > (In reply to John Paul Adrian Glaubitz from comment #1) > > I'll report back tomorrow. > > Problem persists: Correction: The patch

[Bug go/79037] gccgo: Binaries crash with parforsetup: pos is not aligned on m68k

2017-01-10 Thread glaubitz at physik dot fu-berlin.de
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79037 --- Comment #2 from John Paul Adrian Glaubitz --- (In reply to John Paul Adrian Glaubitz from comment #1) > I'll report back tomorrow. Problem persists: root@mama:~# ./hello-world fatal error: parforsetup: pos is not aligned runtime stack:

[Bug go/79037] gccgo: Binaries crash with parforsetup: pos is not aligned on m68k

2017-01-09 Thread glaubitz at physik dot fu-berlin.de
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79037 --- Comment #1 from John Paul Adrian Glaubitz --- Rebuilding gcc with the following change now: --- a/src/libgo/runtime/runtime.h.old 2016-02-12 23:10:09.0 +0100 +++ b/src/libgo/runtime/runtime.h 2017-01-10 00:12:08.404802087