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 for PR69614


On 12 March 2016 at 18:17, Jeff Law <law@redhat.com> wrote:
> On 03/12/2016 07:56 AM, Vladimir Makarov wrote:
>>
>>    The following patch should solve the PR which is discussed on
>>
>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69614
>>
>>    The patch was bootstrapped and tested on x86/x86-64.
>>
>>    Committed as rev. 234162.
>>

Hi Vladimir,

I've noticed that the newly introduced testcase fails on
armeb-none-linux-gnueabihf,
with GCC configured as:
--with-cpu=cortex-a9 --with-fpu=neon-fp16
whether --with-mode=arm or thumb,
but the test passes if GCC is configured --with-fpu=vfpv3-d16-fp16

I'm using qemu, and the test prints:
000000cef0a2b644
instead of the expected value.

Do you prefer me to update bugzilla with this information?

Thanks,

Christophe.

> Isn't this potentially a problem for the gcc-4.9 and gcc-5 release branches?
>
> I'm going to add regression markers for those and drop the gcc-6 regression
> marker.
>
> jeff


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