public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "falk at debian dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/16962] loop unrolling with x86-64 asm not efficient
Date: Tue, 10 Aug 2004 14:09:00 -0000 [thread overview]
Message-ID: <20040810140902.9033.qmail@sourceware.org> (raw)
In-Reply-To: <20040810134244.16962.tomstdenis@iahu.ca>
------- Additional Comments From falk at debian dot org 2004-08-10 14:08 -------
Please use the attachment function for large files in the future. Note also
we don't want assembly output anyway (as stated on http://gcc.gnu.org/bugs.html).
Loop work is currently only being done at the lno-branch. It would be nice
if you could test it there.
Also, this way of unrolling loops doesn't seem fundamentally wrong to me
Can you provide performance numbers that show that it is worse?
--
What |Removed |Added
----------------------------------------------------------------------------
Component|c |tree-optimization
GCC build triplet|gcc version 3.4.1 (Gentoo |x86_86-linux
|Linux 3.4.1, ssp-3.4-2, pie-|
|8.7.6.3) |
GCC host triplet|Linux timmy 2.6.7-gentoo-r11|x86_86-linux
|#1 Thu Aug 5 01:49:49 UTC |
|2004 x86_ |
GCC target triplet|gcc version 3.4.1 (Gentoo |x86_86-linux
|Linux 3.4.1, ssp-3.4-2, pie-|
|8.7.6.3) |
Keywords| |missed-optimization
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16962
next prev parent reply other threads:[~2004-08-10 14:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-10 13:42 [Bug c/16962] New: " tomstdenis at iahu dot ca
2004-08-10 14:09 ` falk at debian dot org [this message]
2004-08-10 14:10 ` [Bug tree-optimization/16962] " falk at debian dot org
2004-08-10 14:13 ` tomstdenis at iahu dot ca
2004-08-10 14:23 ` pinskia at gcc dot gnu dot org
2004-08-10 14:55 ` falk at debian dot org
2004-08-24 21:06 ` falk at debian 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=20040810140902.9033.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).