public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl dot tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/39840] Non-optimal (or wrong) implementation of SSE intrinsics
Date: Wed, 22 Apr 2009 13:58:00 -0000 [thread overview]
Message-ID: <20090422135820.8544.qmail@sourceware.org> (raw)
In-Reply-To: <bug-39840-700@http.gcc.gnu.org/bugzilla/>
------- Comment #8 from hjl dot tools at gmail dot com 2009-04-22 13:58 -------
(In reply to comment #7)
> The problem with different instruction sets in different BBs is also how to
> avoid code motion across them. IMNSHO this is a bad idea.
>
I agree. There are too many issues with it. I'd like to see
function level optimization work properly for all cases.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39840
next prev parent reply other threads:[~2009-04-22 13:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-21 19:05 [Bug middle-end/39840] New: " drepper at redhat dot com
2009-04-21 19:08 ` [Bug middle-end/39840] " hjl dot tools at gmail dot com
2009-04-21 19:38 ` drepper at redhat dot com
2009-04-21 19:41 ` Andrew Thomas Pinski
2009-04-21 19:42 ` pinskia at gmail dot com
2009-04-21 19:51 ` drepper at redhat dot com
2009-04-21 20:34 ` hjl dot tools at gmail dot com
2009-04-21 21:57 ` hjl dot tools at gmail dot com
2009-04-22 9:37 ` rguenth at gcc dot gnu dot org
2009-04-22 13:58 ` hjl dot tools at gmail dot com [this message]
[not found] <bug-39840-4@http.gcc.gnu.org/bugzilla/>
2021-11-29 6:47 ` pinskia at gcc dot gnu.org
2024-03-20 6:29 ` pinskia at gcc dot gnu.org
2024-03-20 6: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=20090422135820.8544.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).