This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] Proposed fix for bug #31899
- From: Mark Mitchell <mark at codesourcery dot com>
- To: Diego Novillo <dnovillo at google dot com>
- Cc: "Doug Kwan (Ãö®¶¼w)" <dougkwan at google dot com>, Daniel Berlin <dberlin at dberlin dot org>, gcc-patches at gcc dot gnu dot org, Jan Hubicka <jh at suse dot cz>
- Date: Sun, 05 Aug 2007 20:19:23 -0700
- Subject: Re: [PATCH] Proposed fix for bug #31899
- References: <498552560707311623n59a20a21ve83cccf4d5583adc@mail.gmail.com> <4aca3dc20707312205g5ac078e3v1a1e72c01206ab3b@mail.gmail.com> <498552560707312248q65b63330j1b07692e090fe308@mail.gmail.com> <46B38262.6000800@google.com>
Diego Novillo wrote:
> For 4.2, Jan agrees that this fix is safe enough. The only risk is that
> DWARF2 may consider a variable both optimized out and directly
> referenced. But given that this has not occurred too frequently, it may
> not be such a big deal.
>
> Doug, the patch is fine for 4.2. One minor nit with the changelog entry:
Please don't put the patch in for 4.2 without a fix for mainline.
Otherwise, we risk regressing in 4.3. Obviously, we don't want 4.2.2 to
have this bug, but we need a plan here.
If this patch is OK for 4.2, as a work-around, can we just put it into
4.3 as well? Or, Doug, are you willing to work on the queuing code for
4.3? I would be happy to review that.
Thanks,
--
Mark Mitchell
CodeSourcery
mark@codesourcery.com
(650) 331-3385 x713