public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: kostadindabov@terascale-euro.com
To: gcc-gnats@gcc.gnu.org
Subject: target/8795: Altivec realted bugs concerning gcc3.2.1 and gcc3.3
Date: Tue, 03 Dec 2002 06:56:00 -0000	[thread overview]
Message-ID: <20021203145504.560.qmail@sources.redhat.com> (raw)


>Number:         8795
>Category:       target
>Synopsis:       Altivec realted bugs concerning gcc3.2.1 and gcc3.3
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Dec 03 06:56:06 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     Kostadin Dabov
>Release:        3.2.1(1 bug), 3.3(2 bugs)
>Organization:
>Environment:
powerpc-yellowdog-linux-gnu(yellowdog 2.3), binutils 2.13				
>Description:
1) The compiler crashes with segmentation fault when compiling simple Altivec and C++ code. This bug is present in 3.2(release), 3.2.1(release), 3.3(latest form gcc cvs, 1Dec2002). The example is in test.cpp
2) This bug applies only to g++(gcc -xc++), only for the 3.3 (latest source from CVS) current stage. When initializing vector values, the compiler will report:
error: brace-enclosed initializer used to initialize 'vector ...'
the example test.cpp illustartes this problem also.
Note that the second bug applies only to g++3.3
>How-To-Repeat:
g++ -maltivec -static -otest test.cpp
or
gcc -xc++ -maltivec -static -otest test.cpp
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


                 reply	other threads:[~2002-12-03 14:56 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20021203145504.560.qmail@sources.redhat.com \
    --to=kostadindabov@terascale-euro.com \
    --cc=gcc-gnats@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).