public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/31485] C complex numbers, amd64 SSE, missed optimization opportunity
Date: Sat, 02 Aug 2008 12:23:00 -0000 [thread overview]
Message-ID: <20080802122142.22762.qmail@sourceware.org> (raw)
In-Reply-To: <bug-31485-2551@http.gcc.gnu.org/bugzilla/>
------- Comment #3 from rguenth at gcc dot gnu dot org 2008-08-02 12:21 -------
Operations in loops should now be vectorized. The original testcase is
probably not worth vectorizing due to calling convention problems (_Complex T
is not passed as a vector).
Complex lowering could generate vectorized code directly though for operations
not in a loop.
--
rguenth at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Ever Confirmed|0 |1
Last reconfirmed|0000-00-00 00:00:00 |2008-08-02 12:21:42
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31485
next prev parent reply other threads:[~2008-08-02 12:23 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-05 11:29 [Bug rtl-optimization/31485] New: " bisqwit at iki dot fi
2007-04-09 17:48 ` [Bug rtl-optimization/31485] " rguenth at gcc dot gnu dot org
2008-07-29 22:07 ` victork at gcc dot gnu dot org
2008-08-02 12:23 ` rguenth at gcc dot gnu dot org [this message]
2008-08-02 13:01 ` ubizjak at gmail dot com
2008-08-02 13:19 ` rguenth at gcc dot gnu dot org
2010-04-17 0:28 ` ddesics at gmail dot com
2010-04-17 11:11 ` rguenth at gcc dot gnu dot org
2010-04-21 11:33 ` irar at il dot ibm dot com
2010-04-21 11:44 ` rguenther at suse dot de
2010-04-21 18:34 ` irar at il dot ibm dot com
[not found] <bug-31485-4@http.gcc.gnu.org/bugzilla/>
2020-04-21 6:43 ` bisqwit at iki dot fi
2020-04-21 7:07 ` rguenth at gcc dot gnu.org
2020-04-21 7:17 ` bisqwit at iki dot fi
2020-04-21 7:37 ` rguenth at gcc dot gnu.org
2020-04-21 8:18 ` bisqwit at iki dot fi
2020-04-21 8:23 ` jakub at gcc dot gnu.org
2020-04-21 8:29 ` rguenther at suse dot de
2020-04-21 8:32 ` jakub at gcc dot gnu.org
2020-04-21 8:33 ` jakub at gcc dot gnu.org
2020-04-21 8:34 ` bisqwit at iki dot fi
2020-04-21 8:43 ` jakub at gcc dot gnu.org
2020-04-21 8:47 ` rguenther at suse dot de
2020-04-21 8:51 ` bisqwit at iki dot fi
2020-04-21 8:58 ` jakub at gcc dot gnu.org
2020-04-21 9:06 ` bisqwit at iki dot fi
2021-08-16 21:29 ` pinskia at gcc dot gnu.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=20080802122142.22762.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).