public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vmakarov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/55150] Crash in copy_rtx Date: Fri, 02 Nov 2012 14:45:00 -0000 [thread overview] Message-ID: <bug-55150-4-vlZELTAvN7@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-55150-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55150 --- Comment #6 from Vladimir Makarov <vmakarov at gcc dot gnu.org> 2012-11-02 14:44:24 UTC --- Author: vmakarov Date: Fri Nov 2 14:44:12 2012 New Revision: 193096 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=193096 Log: 2012-11-02 Vladimir Makarov <vmakarov@redhat.com> PR middle-end/55130 * lra-constraints.c (debug_loc_equivalence_change_p): Rename to loc_equivalence_change_p. (lra_constraints): Check equiv_insn_bitmap for debug insn. Call loc_equivalence_change_p for non-transformed insn. 2012-11-02 Vladimir Makarov <vmakarov@redhat.com> PR middle-end/55150 * gcc.target/i386/pr55130.c: New test. Added: trunk/gcc/testsuite/gcc.target/i386/pr55130.c Modified: trunk/gcc/ChangeLog trunk/gcc/lra-constraints.c trunk/gcc/testsuite/ChangeLog
next prev parent reply other threads:[~2012-11-02 14:45 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-10-31 16:40 [Bug middle-end/55150] New: " rmansfield at qnx dot com 2012-10-31 16:41 ` [Bug middle-end/55150] " rmansfield at qnx dot com 2012-10-31 18:41 ` vmakarov at gcc dot gnu.org 2012-11-01 11:47 ` rmansfield at qnx dot com 2012-11-01 11:48 ` rmansfield at qnx dot com 2012-11-01 19:03 ` vmakarov at gcc dot gnu.org 2012-11-02 14:45 ` vmakarov at gcc dot gnu.org [this message] 2013-12-17 16:24 ` rmansfield at qnx dot com
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-55150-4-vlZELTAvN7@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).