public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "matoro_gcc_bugzilla at matoro dot tk" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug go/103847] New: gccgo SIGSEGV in libgo standard library on sparc64 Date: Mon, 27 Dec 2021 22:59:40 +0000 [thread overview] Message-ID: <bug-103847-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103847 Bug ID: 103847 Summary: gccgo SIGSEGV in libgo standard library on sparc64 Product: gcc Version: 11.2.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: go Assignee: ian at airs dot com Reporter: matoro_gcc_bugzilla at matoro dot tk CC: cmang at google dot com Target Milestone: --- $ go version go version go1.16.5 gccgo (Gentoo 11.2.1_p20211127 p2) 11.2.1 20211127 linux/sparc64 $ gccgo -v Using built-in specs. COLLECT_GCC=gccgo COLLECT_LTO_WRAPPER=/usr/libexec/gcc/sparc64-unknown-linux-gnu/11.2.1/lto-wrapper Target: sparc64-unknown-linux-gnu Configured with: /var/tmp/portage/sys-devel/gcc-11.2.1_p20211127/work/gcc-11-20211127/configure --host=sparc64-unknown-linux-gnu --build=sparc64-unknown-linux-gnu --prefix=/usr --bindir=/usr/sparc64-unknown-linux-gnu/gcc-bin/11.2.1 --includedir=/usr/lib/gcc/sparc64-unknown-linux-gnu/11.2.1/include --datadir=/usr/share/gcc-data/sparc64-unknown-linux-gnu/11.2.1 --mandir=/usr/share/gcc-data/sparc64-unknown-linux-gnu/11.2.1/man --infodir=/usr/share/gcc-data/sparc64-unknown-linux-gnu/11.2.1/info --with-gxx-include-dir=/usr/lib/gcc/sparc64-unknown-linux-gnu/11.2.1/include/g++-v11 --with-python-dir=/share/gcc-data/sparc64-unknown-linux-gnu/11.2.1/python --enable-languages=c,c++,go --enable-obsolete --enable-secureplt --disable-werror --with-system-zlib --enable-nls --without-included-gettext --disable-libunwind-exceptions --enable-checking=release --with-bugurl=https://bugs.gentoo.org/ --with-pkgversion='Gentoo 11.2.1_p20211127 p2' --disable-esp --enable-libstdcxx-time --with-build-config=bootstrap-lto --enable-shared --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu --disable-multilib --disable-fixed-point --enable-targets=all --enable-libgomp --disable-libssp --disable-libada --disable-cet --disable-systemtap --disable-valgrind-annotations --disable-vtable-verify --disable-libvtv --without-zstd --enable-lto --with-isl --disable-isl-version-check --enable-default-pie --enable-default-ssp Thread model: posix Supported LTO compression algorithms: zlib gcc version 11.2.1 20211127 (Gentoo 11.2.1_p20211127 p2) $ uname -a Linux 5.15.11-gentoo-sparc64 #1 SMP sparc64 sun4v UltraSparc T4 (Niagara4) GNU/Linux I am attempting to build a simple go application using gccgo on this sparc64 host, but keep getting compiler SEGV inside the libgo standard library. This is happening for pretty much all commands except for simple version checks. When trying to build from a fresh clone, the crash seem to be in network related code as dependencies are pulled down. When trying to build in an environment where dependencies are pre-downloaded, the crash seems to be in semaphore synchronization. Both runs were done with GOMAXPROCS=1 in order to make the traceback logs deterministic. I also attempted to bootstrap the gc compiler using gcc, but got the same results. I've attached the crash logs from the two different types of builds I attempted as build-with-network.log and build-without-network.log, respectively.
next reply other threads:[~2021-12-27 22:59 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-27 22:59 matoro_gcc_bugzilla at matoro dot tk [this message] 2021-12-27 23:00 ` [Bug go/103847] " matoro_gcc_bugzilla at matoro dot tk 2021-12-27 23:00 ` matoro_gcc_bugzilla at matoro dot tk 2021-12-27 23:01 ` matoro_gcc_bugzilla at matoro dot tk 2021-12-28 17:47 ` ian at airs dot com 2021-12-29 0:53 ` matoro_gcc_bugzilla at matoro dot tk 2021-12-29 2:49 ` ian at airs dot com 2021-12-29 3:05 ` matoro_gcc_bugzilla at matoro dot tk 2021-12-29 23:53 ` cvs-commit at gcc dot gnu.org 2021-12-30 18:43 ` ian at airs dot com 2022-01-01 5:32 ` cvs-commit at gcc dot gnu.org 2022-01-07 6:38 ` pinskia at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-103847-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).