public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Tim Prince <tprince@computer.org>
To: Константин <oks-mgn@mail.ru>
Cc: gcc@gnu.org, gcc-help@gcc.gnu.org
Subject: Re: Optimizations documentation
Date: Tue, 01 Jan 2008 20:49:00 -0000	[thread overview]
Message-ID: <477AA725.3040602@computer.org> (raw)
In-Reply-To: <E1J9nH0-000Ami-00.oks-mgn-mail-ru@mx27.mail.ru>

ц╚ц▐ц▌ц⌠ц■ц│ц▌ц■ц┴ц▌ wrote:
> Hi!
>
> I ask you to put optimimizations tips for programmers into your documentation site on www. Sure, there are some texts about program optimimization, but you are the only one, who really understand compilation and execution processes and know how to make program faster.
> I read on some site that it would better and quicker to use floats instead of doubles, use unsigned int instead of signed as counters in loops, mark const function parameters when they are and so on. Is it true for GCC (G++)?
> Your compiler makes great optimization, but it'd be better if you explain to programmers how to help to compiler optimize program. For example, some time ago I listened that GCC supports vectorization, but still can't find anything about it, how can I use it in my programs.
> Your site is the right place for such documentation. PLEASE put it on.
> Thank you!
>   
This topic seems more appropriate to the gcc-help mail list.
The on-line docs show a fair effort, although documentation of 
-ftree-vectorize seems difficult to find in a single search:
http://gcc.gnu.org/onlinedocs/

Superior performance of float over double is more marked for the SSE 
platforms, so you should specify your platform of interest when asking 
such questions.
If you want examples, quite a few of those are available on line.

           reply	other threads:[~2008-01-01 20:49 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <E1J9nH0-000Ami-00.oks-mgn-mail-ru@mx27.mail.ru>]

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=477AA725.3040602@computer.org \
    --to=tprince@computer.org \
    --cc=gcc-help@gcc.gnu.org \
    --cc=gcc@gnu.org \
    --cc=oks-mgn@mail.ru \
    /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).