This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [patch][4.0] PR 21171
- From: Paul Schlie <schlie at comcast dot net>
- To: Richard Earnshaw <rearnsha at gcc dot gnu dot org>,Zdenek Dvorak <rakdver at atrey dot karlin dot mff dot cuni dot cz>,Mark Mitchell <mark at codesourcery dot com>,gcc-patches <gcc-patches at gcc dot gnu dot org>
- Date: Mon, 13 Jun 2005 11:14:50 -0400
- Subject: Re: [patch][4.0] PR 21171
> Richard Earnshaw wrote:
>> On Mon, 2005-06-13 at 14:12, Zdenek Dvorak wrote:
>> is the patch for that PR (misscompilation due to misshandling of
>> alias info for volatile memory references and memory references
>> with absolute address in ivopts)
>>
>> http://gcc.gnu.org/ml/gcc-patches/2005-04/msg02750.html
>
> The use of volatile in this test was always a red herring. The code
> should execute correctly even when the variables aren't volatile
> qualified. Your patch (IIRC) only addresses the volatile issue so,
> while it might be useful in some real cases, doesn't really fix this
> particular problem.
Should READONLY object reference correctness also be somewhat similarly
maintained here, or elsewhere?