public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ktkachov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/61749] arm_neon.h "_lane" and "_n" intrinsics can cause ICEs Date: Tue, 08 Jul 2014 14:52:00 -0000 [thread overview] Message-ID: <bug-61749-4-o545lD3ZSy@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-61749-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61749 ktkachov at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ktkachov at gcc dot gnu.org --- Comment #2 from ktkachov at gcc dot gnu.org --- Confirmed, also the testcase would be: #include "arm_neon.h" int32x4_t foo (int32x4_t a, int16x4_t b, int16x4_t c, int d) { return vqdmlal_lane_s16 (a, b, c, d); }
next prev parent reply other threads:[~2014-07-08 14:52 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-07-08 14:46 [Bug target/61749] New: " jgreenhalgh at gcc dot gnu.org 2014-07-08 14:47 ` [Bug target/61749] " jgreenhalgh at gcc dot gnu.org 2014-07-08 14:52 ` ktkachov at gcc dot gnu.org [this message] 2014-08-06 16:01 ` ktkachov at gcc dot gnu.org 2014-09-09 10:16 ` ktkachov at gcc dot gnu.org 2014-10-28 10:53 ` ramana at gcc dot gnu.org 2014-12-04 13:25 ` yroux 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-61749-4-o545lD3ZSy@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).