On Tue, Apr 19, 2011 at 11:32 AM, Richard Guenther
wrote:
> On Tue, Apr 12, 2011 at 6:18 PM, Jeff Law wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> On 04/07/11 04:47, Bernd Schmidt wrote:
>>> PR47976 is a followup to PR47166; the patch there caused this problem.
>>>
>>> The pro
On Tue, Apr 12, 2011 at 6:18 PM, Jeff Law wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 04/07/11 04:47, Bernd Schmidt wrote:
>> PR47976 is a followup to PR47166; the patch there caused this problem.
>>
>> The problem occurs in reload. There are two autoinc addresses which
>> inhe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/07/11 04:47, Bernd Schmidt wrote:
> PR47976 is a followup to PR47166; the patch there caused this problem.
>
> The problem occurs in reload. There are two autoinc addresses which
> inherit from one another, and we delete an insn that is necessar
PR47976 is a followup to PR47166; the patch there caused this problem.
The problem occurs in reload. There are two autoinc addresses which
inherit from one another, and we delete an insn that is necessary.
We reach this code when reloading the second autoinc address:
6821 if (optimize &