public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "manu at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/21628] GCC much slower than ICL. Lack of inlining?
Date: Fri, 16 Nov 2007 18:02:00 -0000 [thread overview]
Message-ID: <20071116180202.24863.qmail@sourceware.org> (raw)
In-Reply-To: <bug-21628-3458@http.gcc.gnu.org/bugzilla/>
------- Comment #4 from manu at gcc dot gnu dot org 2007-11-16 18:01 -------
(In reply to comment #2)
> Whaow, I have posted this report for a while...!!!
I guess this report fell through the cracks of bugzilla. Reporting the status
on new versions of GCC would have probably helped.
> But Since version 4.2, GCC seems to respect this attribute, at least!!!
> This was a great improvement for me, I have really waited for this feature.
OK. So this is fixed. Thanks for the report nonetheless. And sorry for the
delay.
> But honestly ICL (Intel Compiler for Windows) is still much better in
> optimisations.
But we are better in freedom. ;-)
--
manu at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|WORKSFORME |FIXED
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21628
next prev parent reply other threads:[~2007-11-16 18:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-21628-3458@http.gcc.gnu.org/bugzilla/>
2007-11-16 15:49 ` manu at gcc dot gnu dot org
2007-11-16 17:46 ` laurent at ient dot rwth-aachen dot de
2007-11-16 18:00 ` rguenth at gcc dot gnu dot org
2007-11-16 18:02 ` manu at gcc dot gnu dot org [this message]
2007-11-16 18:03 ` pcarlini at suse dot de
2007-11-16 20:43 ` laurent at ient dot rwth-aachen dot de
2008-09-27 11:41 ` laurent at ient dot rwth-aachen dot de
2008-09-28 2:12 ` rguenth at gcc dot gnu dot org
2008-09-28 8:01 ` laurent at ient dot rwth-aachen dot de
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=20071116180202.24863.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).