public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "amylaar at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/20070] If-conversion can't match equivalent code, and cross-jumping only works for literal matches Date: Wed, 07 Dec 2005 13:31:00 -0000 [thread overview] Message-ID: <20051207133146.26414.qmail@sourceware.org> (raw) In-Reply-To: <bug-20070-5394@http.gcc.gnu.org/bugzilla/> ------- Comment #22 from amylaar at gcc dot gnu dot org 2005-12-07 13:31 ------- Subject: Bug 20070 Author: amylaar Date: Wed Dec 7 13:31:41 2005 New Revision: 108164 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=108164 Log: 2005-12-07 J"orn Rennecke <joern.rennecke@st.com> Preparation for PR rtl-optimization/20070 / part1 * basic-block.h (insns_match_p, flow_find_cross_jump): Declare. * cfgcleanup.c (condjump_equiv_p): New function, broken out of outgoing_edges_match. (outgoing_edges_match): Use condjump_equiv_p. (merge_memattrs, insns_match_p, flow_find_cross_jump): Move from here into.. * struct-equiv.c: New file. (death_notes_match_p) New function, broken out of insns_match_p. * Makefile.in (OBJS-common): Add struct-equiv.o. (struct-equiv.o): New target. Added: trunk/gcc/struct-equiv.c - copied, changed from r107723, trunk/gcc/cfgcleanup.c Modified: trunk/gcc/ChangeLog trunk/gcc/Makefile.in trunk/gcc/basic-block.h trunk/gcc/cfgcleanup.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20070
next prev parent reply other threads:[~2005-12-07 13:31 UTC|newest] Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-20070-5394@http.gcc.gnu.org/bugzilla/> 2005-12-01 20:17 ` steven at gcc dot gnu dot org 2005-12-07 13:31 ` amylaar at gcc dot gnu dot org [this message] 2005-12-13 13:04 ` amylaar at gcc dot gnu dot org 2005-12-19 14:37 ` amylaar at gcc dot gnu dot org 2006-03-21 8:27 ` bonzini at gnu dot org 2006-03-21 14:24 ` amylaar at gcc dot gnu dot org 2006-11-17 18:58 ` amylaar at gcc dot gnu dot org 2009-06-14 19:54 ` steven at gcc dot gnu dot org 2009-09-04 14:51 ` rahul at icerasemi dot com 2010-01-08 17:08 ` steven at gcc dot gnu dot org 2010-01-09 21:27 ` steven at gcc dot gnu dot org 2010-01-11 12:34 ` rahul at icerasemi dot com 2010-04-23 7:39 ` steven at gcc dot gnu dot org 2005-02-19 15:55 [Bug rtl-optimization/20070] New: " amylaar at gcc dot gnu dot org 2005-02-19 16:03 ` [Bug rtl-optimization/20070] " amylaar at gcc dot gnu dot org 2005-02-19 16:24 ` pinskia at gcc dot gnu dot org 2005-02-21 21:47 ` amylaar at gcc dot gnu dot org 2005-02-21 22:15 ` amylaar at gcc dot gnu dot org 2005-03-02 22:06 ` amylaar at gcc dot gnu dot org 2005-03-03 2:44 ` pinskia at gcc dot gnu dot org 2005-03-03 15:00 ` joern dot rennecke at st dot com 2005-04-05 2:00 ` pinskia at gcc dot gnu dot org 2005-04-12 18:56 ` amylaar at gcc dot gnu dot org 2005-05-26 14:35 ` amylaar at gcc dot gnu dot org 2005-06-01 12:00 ` amylaar at gcc dot gnu dot org 2005-07-07 18:30 ` amylaar at gcc dot gnu dot org 2005-07-12 13:30 ` amylaar at gcc dot gnu dot org 2005-07-12 13:35 ` cvs-commit at gcc dot gnu dot org 2005-07-15 14:22 ` amylaar at gcc dot gnu dot org 2005-07-15 14:43 ` cvs-commit 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=20051207133146.26414.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).