From: Jeff Law <law@redhat.com>
To: Vladimir Makarov <vmakarov@redhat.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: RFA: patch to fix PR48633.
Date: Mon, 23 May 2011 16:12:00 -0000 [thread overview]
Message-ID: <4DDA7CF2.5060303@redhat.com> (raw)
In-Reply-To: <4DCD66BA.6040704@redhat.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 05/13/11 11:13, Vladimir Makarov wrote:
> The patch fixes PR48633 described on
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48633.
>
> The patch was successfully bootstrapped on x86-64.
>
> Ok to commit?
>
> 2011-05-13 Vladimir Makarov <vmakarov@redhat.com>
>
> PR rtl-optimization/48633
> * ira-build.c (loop_with_eh_edge_p): New function.
> (mark_loops_for_removal): Use it.
>
> 2011-05-13 Michael Matz <matz@gcc.gnu.org>
>
> PR rtl-optimization/48633
> * g++.dg/pr48633.C: New test.
OK.
Can you check if this also fixes 48757? According to Uros, it looks
like the same bug.
Jeff
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJN2nzyAAoJEBRtltQi2kC70BwH/3hBSlChl6SQ6k4i3OYCmNRx
FCNLOYEn6fiWzZjAEUc2Jp/3/zb3i2byQ4qFmhd4QSeUamyDzt86WS03VlEg8Rcp
C0SJKZB529U5ijSjby5r4F4ZLw1YPOQhRtKd1y7Pb8w6tPppLqy/6Uw0d5u4S9M6
gZ2B94xEXRrXNqxCgbOLPwaFUSKGVfbjWzuw2pn+7HUfatYM276jKTO6nOLSHQPR
wYQrBv+kGfW5+vQCN3jCwohk3wkLF1oz8TsFSUlZcK7v40KD8MVpEXqjhdjQ8Q+Y
3Dg+d/IhelgLgnYi8OKj4hiYKEaHSJ58Ib4OKAKIfSp2s66ebcq1dBHOKMuIWk0=
=ioWL
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2011-05-23 15:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-13 18:14 Vladimir Makarov
2011-05-23 16:12 ` 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=4DDA7CF2.5060303@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).