From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21727 invoked by alias); 18 Dec 2006 20:06:30 -0000 Received: (qmail 21508 invoked by uid 48); 18 Dec 2006 20:06:15 -0000 Date: Mon, 18 Dec 2006 20:06:00 -0000 Message-ID: <20061218200615.21507.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug c/30254] Need method to determine if AltiVec PIM is available In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "pinskia at gcc dot gnu dot org" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2006-12/txt/msg01547.txt.bz2 ------- Comment #2 from pinskia at gcc dot gnu dot org 2006-12-18 20:06 ------- > 3) Fix __APPLE_ALTIVEC__ so that is is defined in some predicable manner that > can be used for this purpose. Perhaps all you need here is a verification test > case. The problem case appears to be the Cell / Linux GNU tool chain, which > defines __APPLE__ALTIVEC__ without -faltivec or include "altivec.h" This bug really should be reported to IBM rather than the FSF since they release the Cell GNU/Linux toolchains and they are modified versions of GCC. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30254