public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "lh_mouse at 126 dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/97124] ICE when bootstrapping GCC on x86_64-w64-mingw32 Date: Mon, 26 Oct 2020 16:49:43 +0000 [thread overview] Message-ID: <bug-97124-4-ivZZqXhUXM@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97124-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97124 Liu Hao <lh_mouse at 126 dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #7 from Liu Hao <lh_mouse at 126 dot com> --- I received this response from MSYS2 later: ``` jeremyd2019 @jeremyd2019 Oct 26 10:52 how is that back?!? that is caused by a messed up libgmp, and gcc segfaults when it tries to parse a floating point constant (specifically, a messed up libgmp import library, and used via mpfr) gmp patch I sent upstream: https://gmplib.org/list-archives/gmp-bugs/2020-October/004890.html ``` There's a detailed explanation about the cause in the mail linked above, which also answers why this ICE does not always happen. AFAICT this can be closed.
prev parent reply other threads:[~2020-10-26 16:49 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-20 6:16 [Bug bootstrap/97124] New: " lh_mouse at 126 dot com 2020-09-20 10:44 ` [Bug bootstrap/97124] " lh_mouse at 126 dot com 2020-09-21 8:36 ` jakub at gcc dot gnu.org 2020-09-21 10:06 ` lh_mouse at 126 dot com 2020-09-21 10:10 ` jakub at gcc dot gnu.org 2020-09-21 12:07 ` lh_mouse at 126 dot com 2020-10-26 3:36 ` lh_mouse at 126 dot com 2020-10-26 16:49 ` lh_mouse at 126 dot com [this message]
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-97124-4-ivZZqXhUXM@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).