public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "steven at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/30905] [4.3/4.4/4.5 Regression] Fails to cross-jump Date: Sat, 09 Jan 2010 22:17:00 -0000 [thread overview] Message-ID: <20100109221710.18460.qmail@sourceware.org> (raw) In-Reply-To: <bug-30905-10053@http.gcc.gnu.org/bugzilla/> ------- Comment #17 from steven at gcc dot gnu dot org 2010-01-09 22:17 ------- In GCC 4.4 only one crossjump happens. The second crossjump does not happen because the basic blocks are not identical. The register allocator has not allocated the registers in the same way: .L2: movl a, %edx movl a, %eax movl %edx, %ecx movl %eax, %edx andl $3, %ecx andl $3, %edx leal (%ecx,%edx), %edx leal (%edx,%eax), %eax movl %edx, a movl %eax, a movl b, %edx movl b, %eax movl %edx, %ecx movl %eax, %edx orl $3, %ecx orl $3, %edx leal (%ecx,%edx), %edx leal (%edx,%eax), %eax movl %edx, b movl %eax, b jmp .L7 The problem in this case is thus, that there is no pre-RA crossjumping pass anymore. Works for me with my patch for PR20070. -- steven at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- BugsThisDependsOn| |20070 Known to fail| |4.4.0 4.4.1 4.4.2 4.5.0 Summary|[4.3 Regression] Fails to |[4.3/4.4/4.5 Regression] |cross-jump |Fails to cross-jump http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30905
next prev parent reply other threads:[~2010-01-09 22:17 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-02-21 10:04 [Bug middle-end/30905] New: [dataflow] " rguenth at gcc dot gnu dot org 2007-02-21 21:00 ` [Bug middle-end/30905] " steven at gcc dot gnu dot org 2007-02-21 22:09 ` steven at gcc dot gnu dot org 2007-05-08 22:15 ` steven at gcc dot gnu dot org 2007-06-12 19:17 ` [Bug middle-end/30905] [4.3 Regression] " rguenth at gcc dot gnu dot org 2007-06-29 17:58 ` mmitchel at gcc dot gnu dot org 2007-07-04 22:35 ` pinskia at gcc dot gnu dot org 2007-07-05 8:41 ` rguenth at gcc dot gnu dot org 2007-10-16 13:34 ` steven at gcc dot gnu dot org 2008-01-10 19:27 ` steven at gcc dot gnu dot org 2008-01-10 23:18 ` steven at gcc dot gnu dot org 2008-01-11 13:31 ` zadeck at naturalbridge dot com 2008-01-11 14:02 ` rguenth at gcc dot gnu dot org 2008-01-11 14:03 ` stevenb dot gcc at gmail dot com 2008-01-11 15:26 ` rguenth at gcc dot gnu dot org 2008-01-11 15:39 ` steven at gcc dot gnu dot org 2009-06-11 17:38 ` rahul at icerasemi dot com 2009-06-11 19:48 ` steven at gcc dot gnu dot org 2009-06-11 19:49 ` steven at gcc dot gnu dot org 2009-08-04 12:49 ` rguenth at gcc dot gnu dot org 2010-01-09 22:17 ` steven at gcc dot gnu dot org [this message] 2010-02-12 21:12 ` [Bug middle-end/30905] [4.3/4.4/4.5 " steven at gcc dot gnu dot org 2010-03-21 12:04 ` steven 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=20100109221710.18460.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).