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 middle-end/17052] New: altivec varargs failure if no optimization
Date: Mon, 16 Aug 2004 20:10:00 -0000	[thread overview]
Message-ID: <20040816201040.17052.janis187@us.ibm.com> (raw)

Tests gcc.dg/altivec-[237].c fail with a seg fault trying to access
an integer argument that follows a vector float argument.  They fail
without optimization but pass when compiling with -O1 or any higher
level of optimization.  They fail for 32-bit code but not 64-bit code.
The failures begin with the tree-ssa merge.
                                                                                
The test case is extracted from altivec-2.c.  I last tested with
mainline sources as of Mon Aug 16 18:14:11 UTC 2004.

-- 
           Summary: altivec varargs failure if no optimization
           Product: gcc
           Version: 3.5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: middle-end
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: janis187 at us dot ibm dot com
                CC: gcc-bugs at gcc dot gnu dot org
GCC target triplet: powerpc64-unknown-linux-gnu


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


             reply	other threads:[~2004-08-16 20:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-16 20:10 janis187 at us dot ibm dot com [this message]
2004-08-16 20:11 ` [Bug middle-end/17052] " janis187 at us dot ibm dot com
2004-08-16 20:52 ` [Bug middle-end/17052] [3.5 Regression] " pinskia at gcc dot gnu dot org
2004-08-16 21:08 ` janis187 at us dot ibm dot com
2004-08-23  7:58 ` amodra at bigpond dot net dot au
2004-08-23  8:47 ` amodra at bigpond dot net dot au
2004-08-24 14:38 ` [Bug target/17052] " amodra at bigpond dot net dot au
2004-08-25  3:40 ` cvs-commit at gcc dot gnu dot org
2004-08-25  3:46 ` amodra at bigpond dot net dot au

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=20040816201040.17052.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).