public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dje at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/20306] New: [4.0/4.1 Regression] FP complex modes moved via GPRs
Date: Thu, 03 Mar 2005 19:24:00 -0000 [thread overview]
Message-ID: <20050303192352.20306.dje@gcc.gnu.org> (raw)
The patch for PR rtl-opt/15289, changed the behavior of emit_move_insn_1 to
invoke emit_block_move on memory to memory moves for "optimal behavior",
instead of invoking a movMM pattern on the inner mode. emit_block_move
changes the mode to BLKmode masking the original mode. This sequence of
decisions results in GCC choosing GPRs to move a value that explicitly is
declared floating point in the user code, hurting performance.
--
Summary: [4.0/4.1 Regression] FP complex modes moved via GPRs
Product: gcc
Version: 4.0.0
Status: UNCONFIRMED
Keywords: missed-optimization
Severity: normal
Priority: P2
Component: rtl-optimization
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: dje at gcc dot gnu dot org
CC: gcc-bugs at gcc dot gnu dot org,pthaugen at us dot ibm
dot com
GCC build triplet: powerpc*-*-*
GCC host triplet: powerpc*-*-*
GCC target triplet: powerpc*-*-*
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20306
next reply other threads:[~2005-03-03 19:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-03 19:24 dje at gcc dot gnu dot org [this message]
2005-03-03 19:26 ` [Bug rtl-optimization/20306] " dje at gcc dot gnu dot org
2005-03-03 19:38 ` pinskia at gcc dot gnu dot org
2005-03-03 19:48 ` pinskia at gcc dot gnu dot org
2005-03-11 22:59 ` cvs-commit at gcc dot gnu dot org
2005-03-11 23:04 ` cvs-commit at gcc dot gnu dot org
2005-03-21 16:07 ` dje 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=20050303192352.20306.dje@gcc.gnu.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).