From: Jeff Law <law@redhat.com>
To: Vladimir Makarov <vmakarov@redhat.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: RFA: patch for PR48757
Date: Tue, 24 May 2011 22:22:00 -0000 [thread overview]
Message-ID: <4DDC216D.8040707@redhat.com> (raw)
In-Reply-To: <4DDC145E.7060903@redhat.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 05/24/11 14:26, Vladimir Makarov wrote:
> The following patch solves PR48757. It is just a slight modification of
> code for PR48633.
>
> 2011-05-24 Vladimir Makarov <vmakarov@redhat.com>
>
> PR rtl-optimization/48757
> * ira-build.c (loop_with_eh_edge_p): Rename to
> loop_with_complex_edge_p, check edges on complexity, make function
> conditional.
> (mark_loops_for_removal): Make call of loop_with_complex_edge_p
> conditional.
>
> 2011-05-24 Vladimir Makarov <vmakarov@redhat.com>
>
> PR rtl-optimization/48757
> * gfortran.dg/pr48757.f: New test case.
>
>
> The patch was successfully bootstrapped on x86-64.
>
> Ok to commit?
OK.
jeff
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJN3CFtAAoJEBRtltQi2kC78q4H+gJNONmi7W0iMY+ff+oHNUq5
nX8JQMvTJaOLKGdEGBDbg3Dtr1KruRB3EBKM4tyq+Wzwn9lzxCppKJwEJt6IVNMh
dAgy7BrhbWaIGDvAGBqqgMZNNh00UCxPpegLs1pmUc4n0jPYigQqYAtDfeg18mWo
ZOurKAy7JiqWgyKzfos1/b9KKmtrYWTEh9HuPn2DWIJIzEDUIqlXvtNuysHDYIja
N8ycs9RASIOMOtelVgQPOnvObrt17CeIdFz4zka81ftUfOaAQEkhft9ijLHYQkGV
R6LrVKUfmZ4myxryy3pu0LN3wZmt74Y87XUGS7kI8ZOTLIA2xkpbd1weh7kyiO8=
=p73P
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2011-05-24 21:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-24 21:22 Vladimir Makarov
2011-05-24 22:22 ` Jeff Law [this message]
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=4DDC216D.8040707@redhat.com \
--to=law@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=vmakarov@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).