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 tree-optimization/98182] [11 Regression] ICE: Segmentation fault (in gimple_verify_flow_info) Date: Wed, 09 Dec 2020 14:26:10 +0000 [thread overview] Message-ID: <bug-98182-4-7p0insuxEv@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98182-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98182 --- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Martin Liska <marxin@gcc.gnu.org>: https://gcc.gnu.org/g:33d2f41785b24ad43c5a9d52aa289e33ac838f86 commit r11-5883-g33d2f41785b24ad43c5a9d52aa289e33ac838f86 Author: Martin Liska <mliska@suse.cz> Date: Wed Dec 9 15:24:36 2020 +0100 testsuite: fix 2 tests on aarch64 gcc/testsuite/ChangeLog: PR tree-optimization/98182 * gcc.dg/tree-ssa/if-to-switch-1.c: Add case-values-threshold in order to fix them for aarch64. * gcc.dg/tree-ssa/if-to-switch-10.c: Likewise.
next prev parent reply other threads:[~2020-12-09 14:26 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-07 17:03 [Bug tree-optimization/98182] New: " asolokha at gmx dot com 2020-12-08 5:22 ` [Bug tree-optimization/98182] " marxin at gcc dot gnu.org 2020-12-08 12:21 ` marxin at gcc dot gnu.org 2020-12-08 20:03 ` cvs-commit at gcc dot gnu.org 2020-12-08 20:04 ` marxin at gcc dot gnu.org 2020-12-09 12:27 ` clyon at gcc dot gnu.org 2020-12-09 13:34 ` marxin at gcc dot gnu.org 2020-12-09 13:35 ` marxin at gcc dot gnu.org 2020-12-09 13:44 ` clyon at gcc dot gnu.org 2020-12-09 14:26 ` cvs-commit at gcc dot gnu.org [this message] 2020-12-09 14:26 ` marxin 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-98182-4-7p0insuxEv@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).