public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "janis187 at us dot ibm dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/15579] New: tree-ssa regression for C++ altivec tests
Date: Sat, 22 May 2004 22:05:00 -0000	[thread overview]
Message-ID: <20040521233457.15579.janis187@us.ibm.com> (raw)

Several of the C++ altivec tests (g++.dg/ext/altivec-[24568].C) fail
to compile since the tree-ssa merge when no optimization is used.  For
example, altivec-2.C gets the error "argument to `__builtin_altivec_dst'
must be a 2-bit unsigned literal".  In this case a literal '0' is turned
into a var_decl.  The same test is successful when compiled as C instead
of C++.

-- 
           Summary: tree-ssa regression for C++ altivec tests
           Product: gcc
           Version: 3.5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: c++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: janis187 at us dot ibm dot com
                CC: aldyh at redhat dot com,gcc-bugs at gcc dot gnu dot org
  GCC host triplet: powerpc-unknown-linux-gnu
GCC target triplet: powerpc-unknown-linux-gnu


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


             reply	other threads:[~2004-05-21 23:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-22 22:05 janis187 at us dot ibm dot com [this message]
2004-05-22 22:36 ` [Bug tree-optimization/15579] [3.5 Regression] always_inline ignored at -O0 pinskia at gcc dot gnu dot org
2004-05-22 22:52 ` [Bug middle-end/15579] " janis187 at us dot ibm dot com
2004-06-03 23:03 ` steven at gcc dot gnu dot org
2004-09-12  0:43 ` pinskia at gcc dot gnu dot org
2004-11-27  0:51 ` [Bug middle-end/15579] [4.0 " steven 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=20040521233457.15579.janis187@us.ibm.com \
    --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).