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/95731] Faiilure to optimize a >= 0 && b >= 0 to (a | b) >= 0 Date: Thu, 18 Jun 2020 09:19:14 +0000 [thread overview] Message-ID: <bug-95731-4-lQ6CqW6Vdx@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95731-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95731 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Or reassoc could do it across different BBs.
next prev parent reply other threads:[~2020-06-18 9:19 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-17 21:58 [Bug tree-optimization/95731] New: " gabravier at gmail dot com 2020-06-18 8:41 ` [Bug tree-optimization/95731] " rguenth at gcc dot gnu.org 2020-06-18 9:19 ` jakub at gcc dot gnu.org [this message] 2020-08-04 11:21 ` wilco at gcc dot gnu.org 2020-08-04 11:30 ` jakub at gcc dot gnu.org 2021-01-11 14:44 ` [Bug tree-optimization/95731] Failure " jakub at gcc dot gnu.org 2021-01-12 10:05 ` cvs-commit at gcc dot gnu.org 2021-01-16 8:42 ` jakub at gcc dot gnu.org 2021-08-14 21:27 ` pinskia at gcc dot gnu.org 2021-08-14 21:28 ` 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-95731-4-lQ6CqW6Vdx@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).