public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/103253] Unused COND_MUL isn't removed by DCE even with -fno-trapping-math Date: Fri, 06 May 2022 08:31:51 +0000 [thread overview] Message-ID: <bug-103253-4-3iXVJUNC9b@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103253-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103253 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|12.0 |12.2 --- Comment #14 from Jakub Jelinek <jakub at gcc dot gnu.org> --- GCC 12.1 is being released, retargeting bugs to GCC 12.2.
next prev parent reply other threads:[~2022-05-06 8:31 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-15 17:05 [Bug tree-optimization/103253] New: [12 Regression] ICE: Segmentation fault (in convert_mult_to_fma) asolokha at gmx dot com 2021-11-15 17:21 ` [Bug tree-optimization/103253] [12 Regression] ICE: Segmentation fault (in convert_mult_to_fma or in vect_recog_mask_conversion_pattern) asolokha at gmx dot com 2021-11-16 8:16 ` [Bug tree-optimization/103253] [12 Regression] ICE: Segmentation fault (in convert_mult_to_fma or in vect_recog_mask_conversion_pattern) since r12-5129-g8ed62c929c7c4462 marxin at gcc dot gnu.org 2021-11-16 8:27 ` asolokha at gmx dot com 2021-11-16 8:42 ` tnfchris at gcc dot gnu.org 2021-11-16 9:02 ` tnfchris at gcc dot gnu.org 2021-11-16 9:32 ` rguenth at gcc dot gnu.org 2021-11-16 9:39 ` tnfchris at gcc dot gnu.org 2021-11-16 9:44 ` rguenther at suse dot de 2021-11-16 10:12 ` tnfchris at gcc dot gnu.org 2021-11-16 10:29 ` rguenther at suse dot de 2021-11-18 11:24 ` cvs-commit at gcc dot gnu.org 2021-11-18 11:26 ` tnfchris at gcc dot gnu.org 2021-12-13 8:22 ` [Bug tree-optimization/103253] Unused COND_MUL isn't removed by DCE even with -fno-trapping-math tnfchris at gcc dot gnu.org 2022-05-06 8:31 ` jakub at gcc dot gnu.org [this message] 2023-05-08 12:23 ` rguenth 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-103253-4-3iXVJUNC9b@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).