public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "changpeng dot fang at amd dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/44185] [4.6 regression] New prefetch test failures
Date: Fri, 21 May 2010 21:36:00 -0000 [thread overview]
Message-ID: <20100521213604.26072.qmail@sourceware.org> (raw)
In-Reply-To: <bug-44185-682@http.gcc.gnu.org/bugzilla/>
------- Comment #6 from changpeng dot fang at amd dot com 2010-05-21 21:36 -------
(In reply to comment #5)
> The fix introduced:
>
> FAIL: gcc.dg/tree-ssa/prefetch-7.c scan-assembler-times movnti 18
> FAIL: gcc.dg/tree-ssa/prefetch-7.c scan-tree-dump-times optimized "={nt}" 18
>
> on Linux/ia32.
>
It seems the unrolling is quite different for different architecture. The count
of movnti in and assembly code depends on the unroll_factor.
I would propose to remove the movnti check in the assembly code. The dump
in aprefetch shows there are two non-temporal stores generated and this is
enough.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44185
next prev parent reply other threads:[~2010-05-21 21:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-18 2:40 [Bug middle-end/44185] New: " hjl dot tools at gmail dot com
2010-05-18 7:29 ` [Bug middle-end/44185] " hjl dot tools at gmail dot com
2010-05-18 9:56 ` rguenth at gcc dot gnu dot org
2010-05-18 19:39 ` changpeng dot fang at amd dot com
2010-05-20 15:30 ` spop at gcc dot gnu dot org
2010-05-20 15:30 ` spop at gcc dot gnu dot org
2010-05-21 1:41 ` hjl dot tools at gmail dot com
2010-05-21 21:36 ` changpeng dot fang at amd dot com [this message]
2010-05-21 21:46 ` dominiq at lps dot ens dot fr
2010-05-21 21:49 ` hjl dot tools at gmail dot com
2010-06-10 17:55 ` spop at gcc dot gnu dot org
2010-06-17 23:33 ` spop 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=20100521213604.26072.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).