This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH] Fix allocation of reg_known_value

From: Steven Bosscher <stevenb dot gcc at gmail dot com>
To: Paolo Bonzini <bonzini at gnu dot org>
Cc: Uros Bizjak <ubizjak at gmail dot com>, gcc-patches at gcc dot gnu dot org
Date: Fri, 30 Nov 2012 11:42:29 +0100
Subject: Re: [PATCH] Fix allocation of reg_known_value
References: <CAFULd4ZG42Y-yhfKdON2kaheU7LgzMHkspmLLMbCBFT1U-xhpg@mail.gmail.com> <50B88CDF.6030508@gnu.org>

On Fri, Nov 30, 2012 at 11:39 AM, Paolo Bonzini <bonzini@gnu.org> wrote:
> Il 29/11/2012 23:47, Uros Bizjak ha scritto:
>> This one-liner causes following runtime test failure [1] for
>> alphaev68-linux-gnu:
>>
>> FAIL: gfortran.fortran-torture/execute/save_1.f90 execution,  -O2
>> FAIL: gfortran.fortran-torture/execute/save_1.f90 execution,  -O2
>> -fomit-frame-pointer -finline-functions
>> FAIL: gfortran.fortran-torture/execute/save_1.f90 execution,  -O2
>> -fomit-frame-pointer -finline-functions -funroll-loops
>> FAIL: gfortran.fortran-torture/execute/save_1.f90 execution,  -O2
>> -fbounds-check
>>
>> The patch miscompiles libgfortran library.
>>
>> I will provide more info tomorrow, any hint what/where should I look
>> for differences?
>
> Anywhere.  The bug disabled a large part of alias analysis.
>
> Perhaps you can bisect it and backport the fix along the steps.

Or open a PR and assign it to me, ultimately I'm responsible for this breakage.

Ciao!
Steven

Follow-Ups:
- Re: [PATCH] Fix allocation of reg_known_value
  - From: Uros Bizjak

References:
- Re: [PATCH] Fix allocation of reg_known_value
  - From: Uros Bizjak
- Re: [PATCH] Fix allocation of reg_known_value
  - From: Paolo Bonzini

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]