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/55073] Wrong Neon code generation at -O2 caused by -fschedule-insns Date: Fri, 30 Nov 2012 18:50:00 -0000 [thread overview] Message-ID: <bug-55073-4-YPJrzXzijq@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-55073-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55073 Richard Earnshaw <rearnsha at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bernds at gcc dot gnu.org --- Comment #16 from Richard Earnshaw <rearnsha at gcc dot gnu.org> 2012-11-30 18:50:11 UTC --- I need to do some more digging, but it looks like it is the cprop_hardreg pass that is really going wrong. My suspicion is that the pass is seeing vswp D18, D19 // D19 is unused afterwards use D18 and trying to remove the vswp operation entirely, by substituting D19 in for D18, to give: use D19 When doing this it really needs to delete the insn, but it fails to do so. The result is that the code is now incorrect. Bernd, I think you were the last to touch this, can you shed any further light on the issue?
prev parent reply other threads:[~2012-11-30 18:50 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-10-25 12:54 [Bug target/55073] New: " eric.batut at allegorithmic dot com 2012-10-25 23:02 ` [Bug target/55073] " steven at gcc dot gnu.org 2012-11-29 17:52 ` rearnsha at gcc dot gnu.org 2012-11-29 18:05 ` rearnsha at gcc dot gnu.org 2012-11-30 9:52 ` eric.batut at allegorithmic dot com 2012-11-30 9:58 ` rearnsha at gcc dot gnu.org 2012-11-30 10:14 ` eric.batut at allegorithmic dot com 2012-11-30 11:05 ` eric.batut at allegorithmic dot com 2012-11-30 13:21 ` eric.batut at allegorithmic dot com 2012-11-30 14:00 ` rearnsha at gcc dot gnu.org 2012-11-30 14:29 ` eric.batut at allegorithmic dot com 2012-11-30 14:40 ` rearnsha at gcc dot gnu.org 2012-11-30 14:56 ` rearnsha at gcc dot gnu.org 2012-11-30 15:17 ` eric.batut at allegorithmic dot com 2012-11-30 16:18 ` eric.batut at allegorithmic dot com 2012-11-30 16:21 ` eric.batut at allegorithmic dot com 2012-11-30 17:29 ` rearnsha at gcc dot gnu.org 2012-11-30 18:50 ` rearnsha at gcc dot gnu.org [this message]
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-55073-4-YPJrzXzijq@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).