public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/97953] ICE (segfault) during GIMPLE pass: loopdone compiling libgcc/config/libbid/bid128_fma.c:190:1 Date: Thu, 26 Nov 2020 12:56:11 +0000 [thread overview] Message-ID: <bug-97953-4-L4vChu2HU6@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97953-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97953 --- Comment #19 from Martin Liška <marxin at gcc dot gnu.org> --- What a nice reduced test-case. Btw. started to fail with r8-4962-g4aa458f2ac11aef0 with -O2 -fno-tree-free
next prev parent reply other threads:[~2020-11-26 12:56 UTC|newest] Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-23 15:16 [Bug c/97953] New: " chris2553 at googlemail dot com 2020-11-23 15:17 ` [Bug c/97953] " chris2553 at googlemail dot com 2020-11-23 15:20 ` chris2553 at googlemail dot com 2020-11-23 16:21 ` marxin at gcc dot gnu.org 2020-11-23 23:27 ` chris2553 at googlemail dot com 2020-11-24 7:30 ` marxin at gcc dot gnu.org 2020-11-24 8:14 ` [Bug tree-optimization/97953] " rguenth at gcc dot gnu.org 2020-11-24 9:27 ` chris2553 at googlemail dot com 2020-11-24 11:31 ` chris2553 at googlemail dot com 2020-11-24 12:22 ` marxin at gcc dot gnu.org 2020-11-24 13:44 ` rguenth at gcc dot gnu.org 2020-11-24 18:15 ` chris2553 at googlemail dot com 2020-11-24 18:16 ` chris2553 at googlemail dot com 2020-11-25 8:54 ` chris2553 at googlemail dot com 2020-11-25 8:56 ` marxin at gcc dot gnu.org 2020-11-25 8:56 ` marxin at gcc dot gnu.org 2020-11-25 15:23 ` marxin at gcc dot gnu.org 2020-11-25 15:27 ` marxin at gcc dot gnu.org 2020-11-26 12:05 ` rguenth at gcc dot gnu.org 2020-11-26 12:49 ` rguenth at gcc dot gnu.org 2020-11-26 12:56 ` marxin at gcc dot gnu.org [this message] 2020-11-26 12:56 ` marxin at gcc dot gnu.org 2020-11-26 15:18 ` cvs-commit at gcc dot gnu.org 2020-11-26 15:20 ` [Bug tree-optimization/97953] [8/9/10 Regression] " rguenth at gcc dot gnu.org 2020-11-26 17:37 ` chris2553 at googlemail dot com 2021-05-14 9:54 ` [Bug tree-optimization/97953] [9/10 " jakub at gcc dot gnu.org 2021-06-01 8:19 ` rguenth at gcc dot gnu.org 2022-01-12 8:20 ` rguenth at gcc dot gnu.org 2022-01-12 8:21 ` rguenth at gcc dot gnu.org 2022-01-12 8:53 ` cvs-commit at gcc dot gnu.org 2022-01-12 9:21 ` cvs-commit at gcc dot gnu.org 2022-01-12 9:22 ` rguenth at gcc dot gnu.org 2022-01-12 19:53 ` daniel at constexpr dot org 2022-01-12 20:00 ` 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-97953-4-L4vChu2HU6@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).