public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "kazu at cs dot umass dot edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/17652] [meta-bug] GCC 4.1 pending patches Date: Wed, 02 Mar 2005 16:08:00 -0000 [thread overview] Message-ID: <20050302160814.6994.qmail@sourceware.org> (raw) In-Reply-To: <20040924122122.17652.giovannibajo@libero.it> -- Bug 17652 depends on bug 18030, which changed state. Bug 18030 Summary: OR is inefficient in 2-bit bitfield http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18030 What |Old Value |New Value ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17652
next prev parent reply other threads:[~2005-03-02 16:08 UTC|newest] Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-09-24 12:21 [Bug other/17652] New: [metabug] " giovannibajo at libero dot it 2004-09-24 13:01 ` [Bug other/17652] " pinskia at gcc dot gnu dot org 2004-11-02 1:29 ` pinskia at gcc dot gnu dot org 2004-12-04 23:12 ` rth at gcc dot gnu dot org 2004-12-24 19:27 ` pinskia at gcc dot gnu dot org 2005-02-19 15:56 ` [Bug other/17652] [meta-bug] " amylaar at gcc dot gnu dot org 2005-02-25 22:03 ` amylaar at gcc dot gnu dot org 2005-03-02 16:08 ` kazu at cs dot umass dot edu 2005-03-02 16:08 ` kazu at cs dot umass dot edu [this message] 2005-03-02 17:25 ` amylaar at gcc dot gnu dot org 2005-03-02 17:53 ` amylaar at gcc dot gnu dot org 2005-03-02 21:44 ` amylaar at gcc dot gnu dot org 2005-03-07 19:07 ` amylaar at gcc dot gnu dot org 2005-03-07 19:47 ` amylaar at gcc dot gnu dot org 2005-03-07 21:08 ` amylaar at gcc dot gnu dot org 2005-03-07 21:30 ` amylaar at gcc dot gnu dot org 2005-03-07 21:53 ` amylaar at gcc dot gnu dot org 2005-03-08 0:41 ` pinskia at gcc dot gnu dot org 2005-03-08 3:47 ` pinskia at gcc dot gnu dot org 2005-03-08 12:02 ` rth at gcc dot gnu dot org 2005-03-08 14:07 ` pinskia at gcc dot gnu dot org 2005-03-08 14:37 ` pinskia at gcc dot gnu dot org 2005-03-08 14:38 ` pinskia at gcc dot gnu dot org 2005-03-08 15:10 ` amylaar at gcc dot gnu dot org 2005-03-08 19:02 ` avn at any dot ru 2005-03-09 21:16 ` amylaar at gcc dot gnu dot org 2005-03-10 19:59 ` amylaar at gcc dot gnu dot org 2005-03-14 14:40 ` lerdsuwa at gcc dot gnu dot org 2005-03-14 14:53 ` lerdsuwa at gcc dot gnu dot org 2005-03-14 16:18 ` uros at kss-loka dot si 2005-03-15 14:08 ` amylaar at gcc dot gnu dot org 2005-04-12 15:42 ` amylaar at gcc dot gnu dot org 2005-04-12 16:33 ` pinskia at gcc dot gnu dot org 2005-04-12 17:24 ` amylaar at gcc dot gnu dot org 2005-04-12 17:26 ` pinskia at gcc dot gnu dot org 2005-04-12 17:34 ` giovannibajo at libero dot it 2005-04-12 18:03 ` amylaar at gcc dot gnu dot org 2005-04-16 22:02 ` pinskia at gcc dot gnu dot org 2005-04-26 22:21 ` pinskia at gcc dot gnu dot org 2005-05-11 13:19 ` amylaar at gcc dot gnu dot org 2005-07-28 17:17 ` pinskia at gcc dot gnu dot org 2005-09-05 15:46 ` pinskia at gcc dot gnu dot org [not found] <bug-17652-253@http.gcc.gnu.org/bugzilla/> 2005-10-13 20:38 ` steven at gcc dot gnu dot org 2005-10-13 21:35 ` law at redhat dot com 2005-10-13 21:58 ` mark at codesourcery dot com 2005-10-16 22:31 ` 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=20050302160814.6994.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).