public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rakdver at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/18463] [4.0 Regression] Moving floating point through an integer register
Date: Sun, 28 Nov 2004 22:56:00 -0000 [thread overview]
Message-ID: <20041128225609.21368.qmail@sourceware.org> (raw)
In-Reply-To: <20041113170938.18463.steven@gcc.gnu.org>
------- Additional Comments From rakdver at gcc dot gnu dot org 2004-11-28 22:56 -------
I have the (experimental) patch for addressing mode selection on trees
(http://atrey.karlin.mff.cuni.cz/~rakdver/diff_lower_address.diff).
It indeed helps; we get
i = 0;
<L0>:;
mem[aa + 4B * i]{*D.1047} = mem[a + 4B * i]{*D.1048};
mem[bb + 4B * i]{*D.1050} = mem[b + 4B * i]{*D.1051};
i = (int) ((unsigned int) i + 1);
if (n > i) goto <L0>; else goto <L2>;
<L2>:;
in .vars dump and
.L4:
movl (%ebp,%edx,4), %eax
movl %eax, (%esi,%edx,4)
movl (%edi,%edx,4), %eax
movl %eax, (%ebx,%edx,4)
incl %edx
cmpl %edx, %ecx
jg .L4
in the assembler, which seems fine (except that the memory references are not
reordered; maybe some of the aliasing information gets lost due to the patch
currently).
The patch definitely won't make it for 4.0, but I would like to get it or
something similar to 4.1.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18463
next prev parent reply other threads:[~2004-11-28 22:56 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-13 17:09 [Bug middle-end/18463] New: " steven at gcc dot gnu dot org
2004-11-13 17:23 ` [Bug tree-optimization/18463] " pinskia at gcc dot gnu dot org
2004-11-13 17:42 ` pinskia at gcc dot gnu dot org
2004-11-13 17:52 ` steven at gcc dot gnu dot org
2004-11-13 17:54 ` pinskia at gcc dot gnu dot org
2004-11-13 18:14 ` pinskia at gcc dot gnu dot org
2004-11-13 18:46 ` [Bug rtl-optimization/18463] " pinskia at gcc dot gnu dot org
2004-11-13 19:35 ` steven at gcc dot gnu dot org
2004-11-25 23:10 ` cvs-commit at gcc dot gnu dot org
2004-11-25 23:29 ` [Bug tree-optimization/18463] " pinskia at gcc dot gnu dot org
2004-11-25 23:55 ` pinskia at gcc dot gnu dot org
2004-11-26 5:11 ` pinskia at gcc dot gnu dot org
2004-11-26 8:12 ` rakdver at gcc dot gnu dot org
2004-11-28 22:56 ` rakdver at gcc dot gnu dot org [this message]
2004-11-28 23:39 ` giovannibajo at libero dot it
2004-12-05 4:29 ` pinskia at gcc dot gnu dot org
2005-01-29 2:34 ` steven at gcc dot gnu dot org
2005-01-29 2:37 ` [Bug tree-optimization/18463] [4.0 Regression] suboptimal use of fancy x86 addressing modes steven at gcc dot gnu dot org
2005-01-29 3:16 ` tbptbp at gmail dot com
2005-04-21 5:00 ` [Bug tree-optimization/18463] [4.0/4.1 " mmitchel at gcc dot gnu dot org
2005-04-21 7:58 ` rakdver at gcc dot gnu dot org
2005-06-13 12:46 ` pinskia at gcc dot gnu dot org
2005-06-13 13:40 ` jh at suse dot cz
2005-07-08 1:38 ` mmitchel at gcc dot gnu dot org
2005-09-13 18:52 ` [Bug tree-optimization/18463] [4.0 " pinskia at gcc dot gnu dot org
2005-09-14 8:21 ` steven at gcc dot gnu dot org
2005-09-14 11:04 ` rakdver at gcc dot gnu dot org
2005-09-14 12:22 ` rguenth at gcc dot gnu dot org
2005-09-14 12:41 ` rakdver at atrey dot karlin dot mff dot cuni dot cz
2005-09-19 15:20 ` rakdver at gcc dot gnu dot org
2005-09-20 7:09 ` cvs-commit at gcc dot gnu dot org
2005-09-27 16:22 ` mmitchel 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=20041128225609.21368.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).