From: Aldy Hernandez <aldyh@redhat.com>
To: Daniel Egger <degger@fhm.edu>
Cc: GCC Developer Mailinglist <gcc@gcc.gnu.org>
Subject: Re: Altivec conditional?
Date: Wed, 20 Feb 2002 23:50:00 -0000 [thread overview]
Message-ID: <m2bsej1dhh.fsf@culebra.cygnus.com> (raw)
In-Reply-To: Daniel Egger's message of "20 Feb 2002 12:14:20 +0100"
>>>>> "Daniel" == Daniel Egger <degger@fhm.edu> writes:
> Hija,
> I may probably find something in the source after hours of digging but
> probably someone here knows it already. How can I distinguish between
> a GCC having the new altivec builtins and one that has not, i.e. is
> there some preprocessor symbol defined?
__ALTIVEC__
but you have to include <altivec.h>
> I'd really like to cease my C/__asm__ development and use the builtins
> when possible. I also might create a GCC-Altivec-FAQ with the
> experience
the builtins are not supported. Use the convenience macros (and
overloaded C++ functions) defined in <altivec.h>.
*DON'T* use the builtins. The macros are prettier, and i hope to get
rid of the builtins one day...
> gained from being one of the first ones trying to use it productively.
> :)
that would be much appreciated
> --
> Servus,
> Daniel
next prev parent reply other threads:[~2002-02-21 7:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-20 5:39 Daniel Egger
2002-02-20 23:50 ` Aldy Hernandez [this message]
2002-02-21 3:17 ` Daniel Egger
2002-02-21 9:56 ` Daniel Jacobowitz
2002-02-21 16:12 ` Aldy Hernandez
2002-02-22 4:57 ` Daniel Egger
2002-02-22 6:25 ` Jakub Jelinek
2002-02-22 6:26 ` Daniel Egger
2002-02-21 15:47 ` Aldy Hernandez
2002-02-22 5:01 ` Daniel Egger
2002-02-22 14:35 ` Aldy Hernandez
2002-02-22 18:36 ` Geoff Keating
2002-02-23 16:37 ` Daniel Egger
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=m2bsej1dhh.fsf@culebra.cygnus.com \
--to=aldyh@redhat.com \
--cc=degger@fhm.edu \
--cc=gcc@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).