* backported patch for PR69614
@ 2016-03-30 16:15 Vladimir Makarov
2016-03-31 9:56 ` Christophe Lyon
0 siblings, 1 reply; 5+ messages in thread
From: Vladimir Makarov @ 2016-03-30 16:15 UTC (permalink / raw)
To: gcc-patches
The patch for PR69614 has been backported to gcc-5 branch:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69614
Committed as rev. 234577.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: backported patch for PR69614
2016-03-30 16:15 backported patch for PR69614 Vladimir Makarov
@ 2016-03-31 9:56 ` Christophe Lyon
2016-04-01 17:35 ` Vladimir Makarov
0 siblings, 1 reply; 5+ messages in thread
From: Christophe Lyon @ 2016-03-31 9:56 UTC (permalink / raw)
To: Vladimir Makarov; +Cc: gcc-patches
On 30 March 2016 at 18:01, Vladimir Makarov <vmakarov@redhat.com> wrote:
> The patch for PR69614 has been backported to gcc-5 branch:
>
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69614
>
> Committed as rev. 234577.
>
Hi,
As I've already reported:
https://gcc.gnu.org/ml/gcc-patches/2016-03/msg00773.html
the new test executes incorrectly on armeb --with-fpu=neon
Christophe.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: backported patch for PR69614
2016-03-31 9:56 ` Christophe Lyon
@ 2016-04-01 17:35 ` Vladimir Makarov
2016-04-01 17:39 ` Christophe Lyon
0 siblings, 1 reply; 5+ messages in thread
From: Vladimir Makarov @ 2016-04-01 17:35 UTC (permalink / raw)
To: Christophe Lyon; +Cc: gcc-patches
On 03/31/2016 05:35 AM, Christophe Lyon wrote:
> On 30 March 2016 at 18:01, Vladimir Makarov <vmakarov@redhat.com> wrote:
>> The patch for PR69614 has been backported to gcc-5 branch:
>>
>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69614
>>
>> Committed as rev. 234577.
>>
> Hi,
>
> As I've already reported:
> https://gcc.gnu.org/ml/gcc-patches/2016-03/msg00773.html
> the new test executes incorrectly on armeb --with-fpu=neon
>
>
Sorry, I tried to reproduce it on today trunk on a real hardware but
I've failed.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: backported patch for PR69614
2016-04-01 17:35 ` Vladimir Makarov
@ 2016-04-01 17:39 ` Christophe Lyon
2016-04-01 21:36 ` Vladimir Makarov
0 siblings, 1 reply; 5+ messages in thread
From: Christophe Lyon @ 2016-04-01 17:39 UTC (permalink / raw)
To: Vladimir Makarov; +Cc: gcc-patches
On 1 April 2016 at 19:34, Vladimir Makarov <vmakarov@redhat.com> wrote:
> On 03/31/2016 05:35 AM, Christophe Lyon wrote:
>>
>> On 30 March 2016 at 18:01, Vladimir Makarov <vmakarov@redhat.com> wrote:
>>>
>>> The patch for PR69614 has been backported to gcc-5 branch:
>>>
>>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69614
>>>
>>> Committed as rev. 234577.
>>>
>> Hi,
>>
>> As I've already reported:
>> https://gcc.gnu.org/ml/gcc-patches/2016-03/msg00773.html
>> the new test executes incorrectly on armeb --with-fpu=neon
>>
>>
> Sorry, I tried to reproduce it on today trunk on a real hardware but I've
> failed.
>
You have hardware running big-endian natively?
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: backported patch for PR69614
2016-04-01 17:39 ` Christophe Lyon
@ 2016-04-01 21:36 ` Vladimir Makarov
0 siblings, 0 replies; 5+ messages in thread
From: Vladimir Makarov @ 2016-04-01 21:36 UTC (permalink / raw)
To: Christophe Lyon; +Cc: gcc-patches
On 04/01/2016 01:39 PM, Christophe Lyon wrote:
> On 1 April 2016 at 19:34, Vladimir Makarov <vmakarov@redhat.com> wrote:
>> O
>> Sorry, I tried to reproduce it on today trunk on a real hardware but I've
>> failed.
>>
> You have hardware running big-endian natively?
Oops, I missed that it is a big endian machine. Thanks.
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2016-04-01 21:36 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-03-30 16:15 backported patch for PR69614 Vladimir Makarov
2016-03-31 9:56 ` Christophe Lyon
2016-04-01 17:35 ` Vladimir Makarov
2016-04-01 17:39 ` Christophe Lyon
2016-04-01 21:36 ` Vladimir Makarov
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).