public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dberlin at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/15878] a & b & ~a & ~b not optimized at the tree level Date: Sun, 28 Aug 2005 20:04:00 -0000 [thread overview] Message-ID: <20050828200007.15367.qmail@sourceware.org> (raw) In-Reply-To: <20040608183638.15878.pinskia@gcc.gnu.org> ------- Additional Comments From dberlin at gcc dot gnu dot org 2005-08-28 20:00 ------- I have a patch for this -- What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|unassigned at gcc dot gnu |dberlin at gcc dot gnu dot |dot org |org Status|NEW |ASSIGNED Last reconfirmed|2005-05-01 16:29:30 |2005-08-28 20:00:06 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15878
next prev parent reply other threads:[~2005-08-28 20:00 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-06-08 18:36 [Bug tree-optimization/15878] New: " pinskia at gcc dot gnu dot org 2004-06-20 20:38 ` [Bug tree-optimization/15878] " pinskia at gcc dot gnu dot org 2005-07-26 13:16 ` dberlin at gcc dot gnu dot org 2005-08-28 20:04 ` dberlin at gcc dot gnu dot org [this message] [not found] <bug-15878-6528@http.gcc.gnu.org/bugzilla/> 2005-12-13 4:19 ` pinskia at gcc dot gnu dot 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=20050828200007.15367.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).