public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
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: Fri, 22 Feb 2002 14:35:00 -0000	[thread overview]
Message-ID: <5AE05608-27E3-11D6-BCEB-000393750C1E@redhat.com> (raw)
In-Reply-To: <1014382802.5616.7.camel@sonja>


On Saturday, February 23, 2002, at 12:00  AM, Daniel Egger wrote:

> Am Fre, 2002-02-22 um 00.45 schrieb Aldy Hernandez:
>
>> yeah, so download cvs gcc, build it and then use the resulting
>> compiler to compile your code (which should include <altivec.h>)
>
> When I don't have gcc-cvs with altivec.h I cannot include it
> which would mean I have to add additional autoconf hacks to
> every project I touch. I'd prefer something like

i guess i had forgotten to define __ALTIVEC__ from the driver
program-- with specs.  someone else mentioned that this week.

i will fix real soon, so you should be able to do:

	#ifdef __ALTIVEC__
	#include <altivec.h>
	#endif

aldy

  reply	other threads:[~2002-02-22 22:28 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
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 [this message]
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=5AE05608-27E3-11D6-BCEB-000393750C1E@redhat.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).