Re: [PATCH] Fix up testcase.

2020-12-13 Thread Jeff Law via Gcc-patches
On 12/9/20 3:24 AM, Hongtao Liu via Gcc-patches wrote: > On Wed, Dec 9, 2020 at 5:22 PM Prathamesh Kulkarni via Gcc-patches > wrote: >> On Wed, 9 Dec 2020 at 00:29, sunil.k.pandey wrote: >>> On Linux/x86_64, >>> >>> 3a6e3ad38a17a03ee0139b49a0946e7b9ded1eb1 is the first bad commit >>> commit 3a

Re: [PATCH] Fix up testcase.

2020-12-10 Thread Prathamesh Kulkarni via Gcc-patches
On Fri, 11 Dec 2020 at 10:46, Hongtao Liu wrote: > > On Thu, Dec 10, 2020 at 8:52 PM Prathamesh Kulkarni > wrote: > > > > On Wed, 9 Dec 2020 at 15:52, Hongtao Liu wrote: > > > > > > On Wed, Dec 9, 2020 at 5:22 PM Prathamesh Kulkarni via Gcc-patches > > > wrote: > > > > > > > > On Wed, 9 Dec 202

Re: [PATCH] Fix up testcase.

2020-12-10 Thread Hongtao Liu via Gcc-patches
On Thu, Dec 10, 2020 at 8:52 PM Prathamesh Kulkarni wrote: > > On Wed, 9 Dec 2020 at 15:52, Hongtao Liu wrote: > > > > On Wed, Dec 9, 2020 at 5:22 PM Prathamesh Kulkarni via Gcc-patches > > wrote: > > > > > > On Wed, 9 Dec 2020 at 00:29, sunil.k.pandey wrote: > > > > > > > > On Linux/x86_64, >

Re: [PATCH] Fix up testcase.

2020-12-10 Thread Prathamesh Kulkarni via Gcc-patches
On Wed, 9 Dec 2020 at 15:52, Hongtao Liu wrote: > > On Wed, Dec 9, 2020 at 5:22 PM Prathamesh Kulkarni via Gcc-patches > wrote: > > > > On Wed, 9 Dec 2020 at 00:29, sunil.k.pandey wrote: > > > > > > On Linux/x86_64, > > > > > > 3a6e3ad38a17a03ee0139b49a0946e7b9ded1eb1 is the first bad commit > >

[PATCH] Fix up testcase.

2020-12-09 Thread Hongtao Liu via Gcc-patches
On Wed, Dec 9, 2020 at 5:22 PM Prathamesh Kulkarni via Gcc-patches wrote: > > On Wed, 9 Dec 2020 at 00:29, sunil.k.pandey wrote: > > > > On Linux/x86_64, > > > > 3a6e3ad38a17a03ee0139b49a0946e7b9ded1eb1 is the first bad commit > > commit 3a6e3ad38a17a03ee0139b49a0946e7b9ded1eb1 > > Author: Pratha

Re: [PATCH] Fix up testcase (PR tree-optimization/78482)

2016-11-23 Thread Jeff Law
On 11/23/2016 12:36 PM, Jakub Jelinek wrote: Hi! The testcase uses char and can't work properly with unsigned char (otherwise c >= 0 is always true). In addition to that I've noticed that the testcase as is actually doesn't fail with the unfixed gcc, it will just print 2 on stdout. The followi

Re: [PATCH] Fix up testcase (PR tree-optimization/78482)

2016-11-23 Thread Richard Biener
On November 23, 2016 8:36:11 PM GMT+01:00, Jakub Jelinek wrote: >Hi! > >The testcase uses char and can't work properly with unsigned char >(otherwise >c >= 0 is always true). > >In addition to that I've noticed that the testcase as is actually >doesn't >fail with the unfixed gcc, it will just pri

[PATCH] Fix up testcase (PR tree-optimization/78482)

2016-11-23 Thread Jakub Jelinek
Hi! The testcase uses char and can't work properly with unsigned char (otherwise c >= 0 is always true). In addition to that I've noticed that the testcase as is actually doesn't fail with the unfixed gcc, it will just print 2 on stdout. The following has been tested on x86_64-linux and i686-lin