From: Jeff Law <law@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: gcc-patches@gcc.gnu.org, Alexandre Oliva <aoliva@redhat.com>
Subject: Re: [PATCH] Use propagate_threaded_block_debug_into even in loop header copying pass (PR debug/54693)
Date: Tue, 06 Nov 2012 16:43:00 -0000 [thread overview]
Message-ID: <50993E41.2070302@redhat.com> (raw)
In-Reply-To: <20121106110008.GS1881@tucnak.redhat.com>
On 11/06/2012 04:00 AM, Jakub Jelinek wrote:
> Hi!
>
> This patch fixes
> -FAIL: gcc.dg/guality/pr54693-2.c -O1 line 21 i == v + 1
> -FAIL: gcc.dg/guality/pr54693-2.c -O2 line 21 i == v + 1
> -FAIL: gcc.dg/guality/pr54693-2.c -O3 -fomit-frame-pointer line 21 i == v + 1
> -FAIL: gcc.dg/guality/pr54693-2.c -O3 -g line 21 i == v + 1
> -FAIL: gcc.dg/guality/pr54693.c -O1 line 22 i == c - 48
> on both x86_64-linux and i686-linux (and the x/y/z tests in the new testcase
> from UNSUPPORTED to PASS) by copying the debug stmt in ch pass similarly to
> how jump threading does that.
>
> Ok for trunk?
>
> 2012-11-06 Jakub Jelinek <jakub@redhat.com>
>
> PR debug/54693
> * tree-flow.h (propagate_threaded_block_debug_into): New prototype.
> * tree-ssa-threadedge.c (propagate_threaded_block_debug_into): No
> longer static.
> * tree-ssa-loop-ch.c (copy_loop_headers): Use it.
>
> * gcc.dg/guality/pr54693-2.c: New test.
OK.
jeff
next prev parent reply other threads:[~2012-11-06 16:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-06 11:01 Jakub Jelinek
2012-11-06 16:43 ` Jeff Law [this message]
2012-11-06 17:42 ` Alexandre Oliva
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=50993E41.2070302@redhat.com \
--to=law@redhat.com \
--cc=aoliva@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
/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: link
Be 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).