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/101423] [12 Regression] ICE in vect_schedule_slp_node, at tree-vect-slp.c:7113 since r12-1951-ga3aaba68405751ba Date: Tue, 13 Jul 2021 10:59:19 +0000 [thread overview] Message-ID: <bug-101423-4-XBF5PLeOUn@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101423-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101423 --- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-11 branch has been updated by Richard Biener <rguenth@gcc.gnu.org>: https://gcc.gnu.org/g:2d90f3ed9c63926cb6f150aa0dcad4d16a4c16c7 commit r11-8723-g2d90f3ed9c63926cb6f150aa0dcad4d16a4c16c7 Author: Richard Biener <rguenther@suse.de> Date: Mon Jul 12 10:26:25 2021 +0200 middle-end/101423 - internal calls do not trap This adjusts gimple_could_trap_p to not consider internal function calls to trap compared to indirect calls or calls to weak functions. 2021-07-12 Richard Biener <rguenther@suse.de> PR middle-end/101423 * gimple.c (gimple_could_trap_p_1): Internal function calls do not trap. * tree-eh.c (tree_could_trap_p): Likewise. (cherry picked from commit 123d0a597beb6d9865f808bf15b0d67f2a8fd5b2)
prev parent reply other threads:[~2021-07-13 10:59 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-12 4:59 [Bug tree-optimization/101423] New: " marxin at gcc dot gnu.org 2021-07-12 5:00 ` [Bug tree-optimization/101423] " marxin at gcc dot gnu.org 2021-07-12 8:00 ` rguenth at gcc dot gnu.org 2021-07-12 8:24 ` rguenth at gcc dot gnu.org 2021-07-12 8:32 ` rguenth at gcc dot gnu.org 2021-07-12 10:18 ` cvs-commit at gcc dot gnu.org 2021-07-12 10:19 ` rguenth at gcc dot gnu.org 2021-07-13 10:59 ` cvs-commit at gcc dot gnu.org [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-101423-4-XBF5PLeOUn@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).