public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: eyal@mobileye.com
To: gcc-gnats@gcc.gnu.org
Subject: c++/7542: compiling for powerpc Altivec
Date: Thu, 08 Aug 2002 05:16:00 -0000	[thread overview]
Message-ID: <20020808120522.22243.qmail@sources.redhat.com> (raw)


>Number:         7542
>Category:       c++
>Synopsis:       compiling for powerpc Altivec
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          wrong-code
>Submitter-Id:   net
>Arrival-Date:   Thu Aug 08 05:06:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     eyal@mobileye.com
>Release:        gcc-3.1
>Organization:
>Environment:
linux , powerpc 
>Description:
I tried to compile Altivec code - and used vec_msum(__vector signed char c1, __vector unsigned char c2, __vector signed int i1) ... 

the compiler change this to the assembler code vmsumubm - which uses 2 UNsigned char vectors instead of vmsummbm which uses one SIGNES and one UNSIGND !!

this bug causes the signed operand to be treated as unsigned !!
>How-To-Repeat:
the following compilation:
g++ -S -Wall -pedantic -ansi -Wno-long-long -DNDEBUG -O6 -DALTIVEC -maltivec testZevel.cpp

the g++ version is :
Reading specs from /opt/gcc-3.1/lib/gcc-lib/i686-pc-linux-gnu/3.1/specs
Configured with: ../gcc-3.1/configure --prefix=/opt/gcc-3.1 --enable-shared --enable-threads --enable-languages=c,c++
Thread model: posix
gcc version 3.1
>Fix:
need to be find fast so if you have something please let me know !!!
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="testZevel.cpp"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="testZevel.cpp"

I2luY2x1ZGUgPGFsdGl2ZWMuaD4KCl9fdmVjdG9yIHNpZ25lZCBpbnQgdGVzdFpldmVsKCkKeyAg
ICAKICBfX3ZlY3RvciBzaWduZWQgY2hhciB2c2MxID0gey0xNiwtMTUsLTE0LC0xMywtMTIsLTEx
LC0xMCwtOSwtOCwtNywtNiwtNSwtNCwtMywtMiwtMX07CiAgX192ZWN0b3IgdW5zaWduZWQgY2hh
ciB2dWMxID0gezEsMiwzLDQsNSw2LDcsOCw5LDEwLDExLDEyLDEzLDE0LDE1LDE2fTsKICAKICAg
IAogIF9fdmVjdG9yIHNpZ25lZCBpbnQgdnNpMSA9IHswLDAsMCwwfTsKICBfX3ZlY3RvciBzaWdu
ZWQgaW50IHZzaTI7CiAgCiAgdnNpMiA9IHZlY19tc3VtKHZzYzEsdnVjMSx2c2kxKTsKCiAgcmV0
dXJuIHZzaTI7CiAgICAKfQogIAo=


             reply	other threads:[~2002-08-08 12:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-08  5:16 eyal [this message]
2002-09-11 12:03 dje

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=20020808120522.22243.qmail@sources.redhat.com \
    --to=eyal@mobileye.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).