public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "paulus at samba dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/16155] New: Altivec compilation fails with -ansi
Date: Wed, 23 Jun 2004 09:37:00 -0000	[thread overview]
Message-ID: <20040623093015.16155.paulus@samba.org> (raw)

Compilation of a simple altivec test program fails if the -ansi flag is
given to gcc.  When compiled with

gcc -maltivec -c -ansi foo.c

I get the error:

foo.c: In function `foo':
foo.c:6: error: parse error before "typeof"

foo.c contains:

#include <altivec.h>

void foo(void)
{
        vector unsigned short a, b;
        a = vec_splat(b, 0);
}

Without the -ansi flag the compilation succeeds.

-- 
           Summary: Altivec compilation fails with -ansi
           Product: gcc
           Version: 3.3.4
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: c
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: paulus at samba dot org
                CC: gcc-bugs at gcc dot gnu dot org
 GCC build triplet: powerpc-linux
  GCC host triplet: powerpc-linux
GCC target triplet: powerpc-linux


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16155


             reply	other threads:[~2004-06-23  9:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-23  9:37 paulus at samba dot org [this message]
2004-06-23 10:01 ` [Bug c/16155] " segher at kernel dot crashing dot org
2004-06-23 15:19 ` [Bug target/16155] " pinskia at gcc dot gnu dot org
2004-06-24  5:33 ` bje at gcc dot gnu dot org
2004-07-30  6:25 ` bje at gcc dot gnu dot org
2004-07-30  7:02 ` pinskia at gcc dot gnu dot org
2004-07-30 13:51 ` giovannibajo at libero dot it
2004-08-02  1:05 ` cvs-commit at gcc dot gnu dot org
2004-08-02  1:23 ` bje at gcc dot gnu dot org
2004-08-02  1:24 ` pinskia at gcc dot gnu dot org

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=20040623093015.16155.paulus@samba.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).