public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: hartwood@crosslink.net To: gcc-gnats@gcc.gnu.org Subject: other/8551: altivec vec_cmplt generates wrong instruction Date: Tue, 19 Nov 2002 18:05:00 -0000 [thread overview] Message-ID: <20021112192139.24696.qmail@sources.redhat.com> (raw) >Number: 8551 >Category: other >Synopsis: altivec vec_cmplt generates wrong instruction >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: wrong-code >Submitter-Id: net >Arrival-Date: Tue Nov 12 11:26:17 PST 2002 >Closed-Date: >Last-Modified: >Originator: Rick Cellucci >Release: gcc version 3.3 20021104 (experimental) >Organization: >Environment: Configured with: ../gcc3.3/configure --prefix=/usr/local/darwin --enable-altivec --enable-languages=c --with-cpu=7400 --target=powerpc-apple-darwin6.1 >Description: Both vec_cmplt and vec_cmpgt generate the same vcmpgtfp instruction. vec_cmplt should generate vcmpgtfp and switch the second and third arguments, which is not happening. Occurs at any optimization level. I assume short and int versions may be broken as well, I only have tested vector floats. >How-To-Repeat: void VecCmpltIsBroken (void) { vector float zero = (vector float) {0.0, 0.0, 0.0, 0.0}; vector float smaller = (vector float) {1.0, 2.0, 3.0, 4.0}; vector float bigger = (vector float) {5.0, 6.0, 7.0, 8.0}; vector bool int cmp; cmp = vec_cmplt (bigger, smaller); bigger = vec_sel (bigger, zero, cmp); PrintFloatVector (bigger); printf ("\n"); cmp = vec_cmpgt (bigger, smaller); bigger = vec_sel (bigger, zero, cmp); PrintFloatVector (bigger); printf ("\n"); } lvx v31,0,r9 vcmpgtfp v0,v31,v29 vxor v30,v30,v30 vsel v31,v31,v30,v0 vor v2,v31,v31 bl L_PrintFloatVector$stub li r3,10 bl L_putchar$stub vcmpgtfp v0,v31,v29 >Fix: Workaround: Only use vec_cmpgt and switch arguments order in C. >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-11-12 19:26 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-11-19 18:05 hartwood [this message] 2002-12-19 11:49 aldyh
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=20021112192139.24696.qmail@sources.redhat.com \ --to=hartwood@crosslink.net \ --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: linkBe 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).