public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug go/98402] [11 Regression] libgo build broken on arm-linux-gnueabi Date: Tue, 22 Dec 2020 00:18:11 +0000 [thread overview] Message-ID: <bug-98402-4-tiIkJOZBGe@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98402-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98402 --- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Ian Lance Taylor <ian@gcc.gnu.org>: https://gcc.gnu.org/g:03ea48ff27fd40b04b148f7006a02513a887ad0d commit r11-6297-g03ea48ff27fd40b04b148f7006a02513a887ad0d Author: Ian Lance Taylor <iant@golang.org> Date: Mon Dec 21 16:17:23 2020 -0800 Go frontend: ensure mpfr exponent range is large enough for Go PR go/98402 * go-lang.c (go_langhook_init): Force MPFR exponent range to be large enough to support Go constants.
next prev parent reply other threads:[~2020-12-22 0:18 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-20 16:58 [Bug go/98402] New: " doko at debian dot org 2020-12-20 19:42 ` [Bug go/98402] " ian at airs dot com 2020-12-21 7:38 ` doko at debian dot org 2020-12-22 0:18 ` cvs-commit at gcc dot gnu.org [this message] 2020-12-22 4:05 ` 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-98402-4-tiIkJOZBGe@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).