From: Tim Prince <timothyprince@sbcglobal.net>
To: ranjith kumar <ranjit_kumar_b4u@yahoo.co.uk>
Cc: gcc-help@gcc.gnu.org
Subject: Re: vactorization in gcc
Date: Sun, 05 Nov 2006 15:45:00 -0000 [thread overview]
Message-ID: <454E072C.8080209@sbcglobal.net> (raw)
In-Reply-To: <20061105153007.88278.qmail@web27404.mail.ukl.yahoo.com>
ranjith kumar wrote:
> Hi,
> I have read about SIMD(SSE,SSE2....) features of
> Pentium 4.
> I know that one can write code to explioit such a
> feature by using functions in <xmmintrin.h>.....
>
> Given a C program which does not exploit SIMD feature,
> but can be modified to exploit such a feature, can
> GCC optimizer modifies the code to exploit it???
>
> Please send any source to know more about this.
> Thanks in advance.
With so much material on this subject readily available (do you have a
search engine, or access to gcc.gnu.org?), I can't guess what specific
question you have in mind. Did you have trouble spelling the
terminology, e.g. auto-vectorization?
prev parent reply other threads:[~2006-11-05 15:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-05 15:30 ranjith kumar
2006-11-05 15:45 ` Tim Prince [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=454E072C.8080209@sbcglobal.net \
--to=timothyprince@sbcglobal.net \
--cc=gcc-help@gcc.gnu.org \
--cc=ranjit_kumar_b4u@yahoo.co.uk \
--cc=tprince@myrealbox.com \
/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).