From: Daniel Egger <degger@fhm.edu>
To: Michel LESPINASSE <walken@zoy.org>
Cc: Aldy Hernandez <aldyh@redhat.com>, gcc@gcc.gnu.org
Subject: Re: altivec support in gcc - bug with vec_mergel
Date: Tue, 22 Apr 2003 15:11:00 -0000 [thread overview]
Message-ID: <1051013023.1891.19.camel@localhost> (raw)
In-Reply-To: <20030421030614.GB1304@zoy.org>
[-- Attachment #1: Type: text/plain, Size: 659 bytes --]
On Mon, 2003-04-21 at 05:06, Michel LESPINASSE wrote:
> I have some code that compiles and works fine in apple's version of
> gcc 3.1 (as used in darwin) but fails to work when compiled with FSF
> gcc 3.2. Looking at the issue, I think it's due to vec_mergel being
> miscompiled into vmrghh instead of vmrglh. Basically gcc miscompiles
> vec_mergel to do what vec_mergeh should be doing !
2002-02-26 Daniel Egger <degger@fhm.edu>
* config/rs6000/rs6000.md: Swap define_insn attributes to
fix incorrect generation of merge high instructions instead
of merge low.
This one maybe? :)
--
Servus,
Daniel
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-04-22 12:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-08 10:10 altivec support in gcc Michel LESPINASSE
2003-04-09 16:57 ` Aldy Hernandez
2003-04-09 22:55 ` Michel LESPINASSE
2003-04-21 13:30 ` altivec support in gcc - bug with vec_mergel Michel LESPINASSE
2003-04-22 15:11 ` Daniel Egger [this message]
2003-04-22 16:43 ` Michel LESPINASSE
2003-04-22 19:55 ` Daniel Egger
2003-04-22 21:40 ` Aldy Hernandez
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=1051013023.1891.19.camel@localhost \
--to=degger@fhm.edu \
--cc=aldyh@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=walken@zoy.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).