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 debug/42662] [4.5 Regression] invalid rtl sharing found in the insn Date: Mon, 11 Jan 2010 09:47:00 -0000 [thread overview] Message-ID: <20100111094657.23643.qmail@sourceware.org> (raw) In-Reply-To: <bug-42662-9596@http.gcc.gnu.org/bugzilla/> ------- Comment #6 from jakub at gcc dot gnu dot org 2010-01-11 09:46 ------- Created an attachment (id=19537) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=19537&action=view) gcc45-pr42662.patch Fix. Regarding the above mentioned patch, it looks like a big hammer, which will create a lot of garbage. Are you sure you have investigated where exactly the sharing originates from? On the line this patch is fixing XEXP (op0, 0) is used twice, once inside the plus and once as the second comparison operand. So it is clearly where the bug is introduced. Another place which also introduces something similar (x*x scalar floating optimization) already uses properly copy_rtx. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42662
next prev parent reply other threads:[~2010-01-11 9:47 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-01-08 18:09 [Bug c/42662] New: " dcb314 at hotmail dot com 2010-01-08 18:10 ` [Bug c/42662] " dcb314 at hotmail dot com 2010-01-08 18:11 ` [Bug debug/42662] [4.5 Regression] " pinskia at gcc dot gnu dot org 2010-01-09 17:25 ` jakub at gcc dot gnu dot org 2010-01-09 20:35 ` hjl dot tools at gmail dot com 2010-01-11 9:25 ` jakub at gcc dot gnu dot org 2010-01-11 9:36 ` jzhang918 at gmail dot com 2010-01-11 9:47 ` jakub at gcc dot gnu dot org [this message] 2010-01-11 10:11 ` jzhang918 at gmail dot com 2010-01-12 9:46 ` jakub at gcc dot gnu dot org 2010-01-12 9:47 ` jakub at gcc dot gnu dot org 2010-01-13 10:08 ` 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=20100111094657.23643.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).