public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/57431] ICE in simplify_const_unary_operation vld1_dup_s64/vst1_s64 Date: Thu, 08 Aug 2013 13:48:00 -0000 [thread overview] Message-ID: <bug-57431-4-Mgv6XGBjhG@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-57431-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57431 Richard Earnshaw <rearnsha at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED Target Milestone|--- |4.9.0 --- Comment #2 from Richard Earnshaw <rearnsha at gcc dot gnu.org> --- Fixed on trunk with: PR target/57431 * arm/neon.md (neon_vld1_dupdi): New expand pattern. (neon_vld1_dup<mode> VD iterator): Iterate over VD not VDX. Committed to trunk as revision r201599.
next prev parent reply other threads:[~2013-08-08 13:48 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-05-27 11:50 [Bug target/57431] New: " christophe.lyon at st dot com 2013-08-02 15:16 ` [Bug target/57431] " rearnsha at gcc dot gnu.org 2013-08-08 13:48 ` rearnsha at gcc dot gnu.org [this message] 2013-09-05 12:31 ` clyon 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-57431-4-Mgv6XGBjhG@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).