public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "guojiufu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug go/105315] go build fail on ppc: has no member named 'gregs'; did you mean 'regs'? Date: Wed, 20 Apr 2022 01:44:46 +0000 [thread overview] Message-ID: <bug-105315-4-KPQEB5vi8h@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105315-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105315 --- Comment #1 from Jiu Fu Guo <guojiufu at gcc dot gnu.org> --- The failure compiling command is about -m32: /home/guojiufu/gcc/build/gcc-mainline-base/./gcc/xgcc -B/home/guojiufu/gcc/build/gcc-mainline-base/./gcc/ -B/home/guojiufu/gcc/install/gcc-mainline-base/powerpc64-unknown-linux-gnu/bin/ -B/home/guojiufu/gcc/install/gcc-mainline-base/powerpc64-unknown-linux-gnu/lib/ -isystem /home/guojiufu/gcc/install/gcc-mainline-base/powerpc64-unknown-linux-gnu/include -isystem /home/guojiufu/gcc/install/gcc-mainline-base/powerpc64-unknown-linux-gnu/sys-include -m32 -DHAVE_CONFIG_H -I. -I/home/guojiufu/gcc/gcc-mainline-base/libgo -I /home/guojiufu/gcc/gcc-mainline-base/libgo/runtime -I/home/guojiufu/gcc/gcc-mainline-base/libgo/../libffi/include -I../libffi/include -pthread -L../libatomic/.libs -fexceptions -fnon-call-exceptions -Wall -Wextra -Wwrite-strings -Wcast-qual -Werror -D_GNU_SOURCE -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I /home/guojiufu/gcc/gcc-mainline-base/libgo/../libgcc -I /home/guojiufu/gcc/gcc-mainline-base/libgo/../libbacktrace -I ../../../gcc/include -g -O2 -m32 -MT runtime/go-signal.lo -MD -MP -MF runtime/.deps/go-signal.Tpo -c /home/guojiufu/gcc/gcc-mainline-base/libgo/runtime/go-signal.c -fPIC -DPIC -o runtime/.libs/go-signal.o
next prev parent reply other threads:[~2022-04-20 1:44 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-20 1:42 [Bug go/105315] New: " guojiufu at gcc dot gnu.org 2022-04-20 1:44 ` guojiufu at gcc dot gnu.org [this message] 2022-04-21 0:49 ` [Bug go/105315] " cvs-commit at gcc dot gnu.org 2022-04-21 0:50 ` ian at airs dot com 2022-04-21 9:16 ` guojiufu 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-105315-4-KPQEB5vi8h@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).