public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/104149] [12 Regression] trunk 20220120 ftbfs in gotools on x86_64-linux-gnux32
Date: Fri, 21 Jan 2022 00:29:06 +0000 [thread overview]
Message-ID: <bug-104149-4-P4k2Of16Tl@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104149-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104149
H.J. Lu <hjl.tools at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |NEW
--- Comment #4 from H.J. Lu <hjl.tools at gmail dot com> ---
(In reply to Ian Lance Taylor from comment #2)
> We probably just need to add amd64p32 to the go:build and +build lines in
> libgo/go/runtime/panic32.go. But I don't have a way to test that.
It works. Ian, can you apply the patch in comment #3? Thanks.
next prev parent reply other threads:[~2022-01-21 0:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-20 21:01 [Bug go/104149] New: " doko at debian dot org
2022-01-20 22:12 ` [Bug go/104149] " hjl.tools at gmail dot com
2022-01-20 22:24 ` ian at airs dot com
2022-01-21 0:27 ` hjl.tools at gmail dot com
2022-01-21 0:29 ` hjl.tools at gmail dot com [this message]
2022-01-21 3:08 ` ian at airs dot com
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-104149-4-P4k2Of16Tl@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: link
Be 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).