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/104334] [12 Regression] Ranger/dom miscompilation since r12-4694-gcb153222404e2e Date: Wed, 02 Feb 2022 14:12:59 +0000 [thread overview] Message-ID: <bug-104334-4-yDMkkwd3PN@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104334-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104334 --- Comment #19 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Created attachment 52329 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52329&action=edit gcc12-pr104334.patch Patch doing ?h_range and related comparisons in widest_int.
next prev parent reply other threads:[~2022-02-02 14:12 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-01 20:35 [Bug tree-optimization/104334] New: Ranger/dom miscompilation jakub at gcc dot gnu.org 2022-02-01 20:35 ` [Bug tree-optimization/104334] [12 Regression] " jakub at gcc dot gnu.org 2022-02-01 20:48 ` jakub at gcc dot gnu.org 2022-02-02 1:27 ` pinskia at gcc dot gnu.org 2022-02-02 10:18 ` marxin at gcc dot gnu.org 2022-02-02 10:19 ` marxin at gcc dot gnu.org 2022-02-02 10:29 ` pinskia at gcc dot gnu.org 2022-02-02 10:37 ` jakub at gcc dot gnu.org 2022-02-02 12:06 ` jakub at gcc dot gnu.org 2022-02-02 12:13 ` jakub at gcc dot gnu.org 2022-02-02 12:26 ` rsandifo at gcc dot gnu.org 2022-02-02 12:30 ` rguenther at suse dot de 2022-02-02 12:31 ` jakub at gcc dot gnu.org 2022-02-02 12:38 ` [Bug tree-optimization/104334] [12 Regression] Ranger/dom miscompilation since r12-4694-gcb153222404e2e marxin at gcc dot gnu.org 2022-02-02 12:46 ` jakub at gcc dot gnu.org 2022-02-02 12:51 ` marxin at gcc dot gnu.org 2022-02-02 13:39 ` jakub at gcc dot gnu.org 2022-02-02 13:50 ` amacleod at redhat dot com 2022-02-02 13:56 ` rguenther at suse dot de 2022-02-02 14:00 ` jakub at gcc dot gnu.org 2022-02-02 14:12 ` jakub at gcc dot gnu.org [this message] 2022-02-02 15:07 ` rsandifo at gcc dot gnu.org 2022-02-03 8:46 ` cvs-commit at gcc dot gnu.org 2022-02-03 8:46 ` jakub 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-104334-4-yDMkkwd3PN@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).