public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/37812] [4.4 Regression] Invalid mnemonic 'lvlx' Date: Mon, 03 Nov 2008 09:08:00 -0000 [thread overview] Message-ID: <20081103090718.29099.qmail@sourceware.org> (raw) In-Reply-To: <bug-37812-12313@http.gcc.gnu.org/bugzilla/> ------- Comment #5 from jakub at gcc dot gnu dot org 2008-11-03 09:07 ------- Created an attachment (id=16615) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=16615&action=view) gcc44-pr37812.patch Ah, I see, it is a testsuite bug then. altivec_check.h uses the lvlx insns inside of inline assembly unconditionally. There is no reason for that if not -mcpu=cell and when -mcpu=cell is used, the user and/or testcase should better make sure the assembler supports cell. Which leads to another bug, we need a new target-supports tcl function and guard all the -mcpu=cell tests with it (say powerpc_cell_ok or powerpc_ppu_ok, which would imply powerpc_altivec_ok and that these insns can be assembled). -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37812
next prev parent reply other threads:[~2008-11-03 9:08 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-10-12 23:03 [Bug target/37812] New: " dominiq at lps dot ens dot fr 2008-10-12 23:06 ` [Bug target/37812] " pinskia at gcc dot gnu dot org 2008-11-01 11:42 ` rguenth at gcc dot gnu dot org 2008-11-01 21:06 ` ubizjak at gmail dot com 2008-11-03 8:16 ` jakub at gcc dot gnu dot org 2008-11-03 8:22 ` dominiq at lps dot ens dot fr 2008-11-03 9:08 ` jakub at gcc dot gnu dot org [this message] 2008-11-03 9:51 ` jakub at gcc dot gnu dot org 2008-11-03 17:32 ` dominiq at lps dot ens dot fr 2008-11-03 17:45 ` jakub at gcc dot gnu dot org 2008-11-03 22:02 ` jakub at gcc dot gnu dot org 2008-11-03 22:09 ` jakub at gcc dot gnu dot org
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=20081103090718.29099.qmail@sourceware.org \ --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: 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).