Re: [committed] Handle targets with 2 byte wchar_t better in strlenopt-58.c

2018-12-05 Thread Martin Sebor
On 12/5/18 12:13 PM, Jeff Law wrote: On 12/5/18 11:59 AM, David Edelsohn wrote: Jeff, Thanks for the patch. I continue to see a failure on AIX 32 bit mode (2 byte wchar). FAIL: gcc.dg/strlenopt-58.c scan-tree-dump-times optimized "call_in_true_branch_not_eliminated" 0 I'm not certain if this

Re: [committed] Handle targets with 2 byte wchar_t better in strlenopt-58.c

2018-12-05 Thread Jeff Law
On 12/5/18 11:59 AM, David Edelsohn wrote: > Jeff, > > Thanks for the patch. > > I continue to see a failure on AIX 32 bit mode (2 byte wchar). > > FAIL: gcc.dg/strlenopt-58.c scan-tree-dump-times optimized > "call_in_true_branch_not_eliminated" 0 > > I'm not certain if this is AIX-specific or

Re: [committed] Handle targets with 2 byte wchar_t better in strlenopt-58.c

2018-12-05 Thread David Edelsohn
Jeff, Thanks for the patch. I continue to see a failure on AIX 32 bit mode (2 byte wchar). FAIL: gcc.dg/strlenopt-58.c scan-tree-dump-times optimized "call_in_true_branch_not_eliminated" 0 I'm not certain if this is AIX-specific or more fallout from wchar size. I could ignore with target power

[committed] Handle targets with 2 byte wchar_t better in strlenopt-58.c

2018-12-04 Thread Jeff Law
This is another minor testsuite patch. strlenopt-58.c assumes 4 byte wchar_t. On targets with a smaller wchar_t it will get an error/warning. This patch adds a dg-warning on the appropriate lines for targets that do not have 4byte wchar_t. It's been tested on h8 to verify the bogus warnings/e