public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug pending/41998] GCC 4.6 pending patches meta-bug
Date: Fri, 16 Apr 2010 23:05:00 -0000 [thread overview]
Message-ID: <20100416230506.27405.qmail@sourceware.org> (raw)
In-Reply-To: <bug-41998-391@http.gcc.gnu.org/bugzilla/>
------- Comment #14 from law at redhat dot com 2010-04-16 23:05 -------
Most of the h8_enhancement patch has been applied. Unfortunately, one aspect
of that change (reordering alternatives in the logical and, ior, xor patterns)
causes codesize & performance regressions and has not been installed. The
fundamental problem is the bit insns do not set cc0 and as a result we often
miss opportunities to remove tst insns.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41998
next prev parent reply other threads:[~2010-04-16 23:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-10 16:58 [Bug pending/41998] New: " law at redhat dot com
2009-11-10 17:15 ` [Bug pending/41998] " law at redhat dot com
2009-11-10 23:00 ` law at redhat dot com
2009-11-19 0:05 ` law at redhat dot com
2009-12-02 17:41 ` law at redhat dot com
2009-12-05 17:15 ` aesok at gcc dot gnu dot org
2010-02-09 6:08 ` steven at gcc dot gnu dot org
2010-02-17 16:33 ` amonakov at gcc dot gnu dot org
2010-02-26 13:55 ` kaushik dot phatak at kpitcummins dot com
2010-02-27 18:45 ` manu at gcc dot gnu dot org
2010-02-27 18:48 ` manu at gcc dot gnu dot org
2010-03-03 12:54 ` kaushik dot phatak at kpitcummins dot com
2010-03-03 14:32 ` manu at gcc dot gnu dot org
2010-03-11 9:08 ` kaushik dot phatak at kpitcummins dot com
2010-03-11 12:51 ` manu at gcc dot gnu dot org
2010-04-16 23:05 ` law at redhat dot com [this message]
2010-05-04 4:15 ` law at redhat dot com
[not found] <bug-41998-4@http.gcc.gnu.org/bugzilla/>
2011-03-17 16:02 ` law at redhat dot com
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=20100416230506.27405.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: link
Be 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).