public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rmansfield at qnx dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/51534] Bad code gen for vcgtq_u32 NEON intrinsic Date: Tue, 13 Dec 2011 19:53:00 -0000 [thread overview] Message-ID: <bug-51534-4-hNbWxDPpPB@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-51534-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51534 --- Comment #1 from Ryan Mansfield <rmansfield at qnx dot com> 2011-12-13 19:47:28 UTC --- I truncated the actual error emitted by the assembler. $ ./xgcc -B. -O3 -ftree-vectorize -mfpu=neon -mfloat-abi=softfp ~/foo.c -march=armv7-a -c /tmp/ccCPCd9Z.s: Assembler messages: /tmp/ccCPCd9Z.s:30: Error: bad type in Neon instruction -- `vcgt.u32 q11,q9,#0'
next prev parent reply other threads:[~2011-12-13 19:47 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-12-13 19:29 [Bug target/51534] New: " rmansfield at qnx dot com 2011-12-13 19:53 ` rmansfield at qnx dot com [this message] 2011-12-14 15:01 ` [Bug target/51534] " rearnsha at gcc dot gnu.org 2012-02-28 16:15 ` mgretton at gcc dot gnu.org 2012-02-28 16:19 ` mgretton at gcc dot gnu.org 2014-08-10 16:46 ` rmansfield at qnx dot com 2023-03-03 19:10 ` cvs-commit at gcc dot gnu.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=bug-51534-4-hNbWxDPpPB@http.gcc.gnu.org/bugzilla/ \ --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).