public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/27504] x && (x & y) not optimized to x & y Date: Tue, 09 May 2006 06:20:00 -0000 [thread overview] Message-ID: <20060509062002.30883.qmail@sourceware.org> (raw) In-Reply-To: <bug-27504-2744@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from pinskia at gcc dot gnu dot org 2006-05-09 06:20 ------- Confirmed. -- pinskia at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|normal |enhancement Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Last reconfirmed|0000-00-00 00:00:00 |2006-05-09 06:20:01 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27504
next prev parent reply other threads:[~2006-05-09 6:20 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-05-08 19:28 [Bug tree-optimization/27504] New: " falk at debian dot org 2006-05-09 6:20 ` pinskia at gcc dot gnu dot org [this message] 2006-05-09 8:36 ` [Bug tree-optimization/27504] " rguenth at gcc dot gnu dot org [not found] <bug-27504-4@http.gcc.gnu.org/bugzilla/> 2021-06-03 2:43 ` pinskia at gcc dot gnu.org 2023-05-05 8:17 ` pinskia at gcc dot gnu.org 2023-10-12 17:56 ` pinskia at gcc dot gnu.org 2023-10-12 18:00 ` 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=20060509062002.30883.qmail@sourceware.org \ --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).