This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug go/66368] [5 Regression] go tool crashes on powerpc-linux-gnu
- From: "adconrad at 0c3 dot net" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Tue, 02 Jun 2015 20:44:22 +0000
- Subject: [Bug go/66368] [5 Regression] go tool crashes on powerpc-linux-gnu
- Auto-submitted: auto-generated
- References: <bug-66368-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66368
Adam Conrad <adconrad at 0c3 dot net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |adconrad at 0c3 dot net
--- Comment #4 from Adam Conrad <adconrad at 0c3 dot net> ---
No, this is specifically about powerpc-linux-gnu. powerpc64le works fine.
As for the library path questions, this first came up in runtime bug reports,
and has been confirmed by many on clean chroots, so no, there aren't random
libraries kicking around from other builds.
doko's stack-protector discovery makes perfect sense as to why this works fine
on Debian but not Ubuntu, as that's really the only difference between our two
toolchains. Now, the question is *why*, and why only on ppc32? (Or maybe only
on big-endian PPC, neither of us has tested a powerpc64-linux-gnu build yet).