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 rtl-optimization/15792] missed subreg optimization Date: Wed, 18 Jan 2006 04:45:00 -0000 [thread overview] Message-ID: <20060118044550.4882.qmail@sourceware.org> (raw) In-Reply-To: <bug-15792-6528@http.gcc.gnu.org/bugzilla/> ------- Comment #3 from pinskia at gcc dot gnu dot org 2006-01-18 04:45 ------- The problem here is that we don't split up the subregister early before register allocation. If we split it up before combine, we would be able to combine the or and get the more optimial results. A patch like http://gcc.gnu.org/ml/gcc-patches/2005-05/msg00554.html should help. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15792
next parent reply other threads:[~2006-01-18 4:45 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-15792-6528@http.gcc.gnu.org/bugzilla/> 2006-01-18 4:45 ` pinskia at gcc dot gnu dot org [this message] 2006-01-20 15:48 ` tony dot linthicum at amd dot com 2006-01-20 15:52 ` pinskia at gcc dot gnu dot org 2006-02-02 18:18 ` ian at airs dot com 2006-02-06 17:13 ` tony dot linthicum at amd dot com 2006-02-07 0:30 ` ian at airs dot com 2006-02-07 8:23 ` ian at airs dot com 2007-11-10 0:15 ` rask at gcc dot gnu dot org [not found] <bug-15792-4@http.gcc.gnu.org/bugzilla/> 2021-10-15 3:00 ` gabravier at gmail dot com 2023-05-15 5:34 ` pinskia at gcc dot gnu.org 2004-06-03 4:27 [Bug rtl-optimization/15792] New: " pinskia at gcc dot gnu dot org 2004-06-15 20:07 ` [Bug rtl-optimization/15792] " bangerth at dealii dot org 2004-08-20 18:47 ` dann at godzilla dot ics dot uci dot edu
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=20060118044550.4882.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).