From: Falk Hueffner <falk.hueffner@student.uni-tuebingen.de>
To: "Kaspar Thommen" <kaspar@gmx.ch>
Cc: gcc-help@gcc.gnu.org
Subject: Re: g++ V3.3.1 not faster with __restrict
Date: Fri, 21 Nov 2003 10:42:00 -0000 [thread overview]
Message-ID: <87he0y0zqq.fsf@student.uni-tuebingen.de> (raw)
In-Reply-To: <24123.1069410397@www48.gmx.net>
"Kaspar Thommen" <kaspar@gmx.ch> writes:
> To my surprise, the __restrict version is not faster than the conventional
> one. In fact, they show the same speed. Do I have to specify any compilation
> option to tell g++ to really take advantage from the __restrict information?
No, although probably -O2 is required to show any difference.
> Didn't find anything in the docs however. I tried using -o, -o2,
> -o3, giving always equal speed for both functions.
Try -funroll-loops or -funroll-all-loops, this produces more
possibilities to take advantage of the non-aliasing.
--
Falk
prev parent reply other threads:[~2003-11-21 10:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-21 10:26 Kaspar Thommen
2003-11-21 10:42 ` Falk Hueffner [this message]
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=87he0y0zqq.fsf@student.uni-tuebingen.de \
--to=falk.hueffner@student.uni-tuebingen.de \
--cc=gcc-help@gcc.gnu.org \
--cc=kaspar@gmx.ch \
/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).