Re: [PATCH] libiberty: Make strstr.c in libiberty ANSI compliant

2023-04-02 Thread Jeff Law via Gcc-patches
On 3/29/23 09:00, Jakub Jelinek via Gcc-patches wrote: On Fri, Nov 13, 2020 at 11:53:43AM -0700, Jeff Law via Gcc-patches wrote: On 5/1/20 6:06 PM, Seija Kijin via Gcc-patches wrote: The original code in libiberty says "FIXME" and then says it has not been validated to be ANSI compliant. Ho

Re: [PATCH] libiberty: Make strstr.c in libiberty ANSI compliant

2023-03-29 Thread Jakub Jelinek via Gcc-patches
On Fri, Nov 13, 2020 at 11:53:43AM -0700, Jeff Law via Gcc-patches wrote: > > On 5/1/20 6:06 PM, Seija Kijin via Gcc-patches wrote: > > The original code in libiberty says "FIXME" and then says it has not been > > validated to be ANSI compliant. However, this patch changes the function to > > matc

Re: [PATCH] libiberty: Make strstr.c in libiberty ANSI compliant

2020-11-13 Thread Jeff Law via Gcc-patches
On 5/1/20 6:06 PM, Seija Kijin via Gcc-patches wrote: > The original code in libiberty says "FIXME" and then says it has not been > validated to be ANSI compliant. However, this patch changes the function to > match implementations that ARE compliant, and such code is in the public > domain. > >

[PATCH] libiberty: Make strstr.c in libiberty ANSI compliant

2020-05-01 Thread Seija Kijin via Gcc-patches
The original code in libiberty says "FIXME" and then says it has not been validated to be ANSI compliant. However, this patch changes the function to match implementations that ARE compliant, and such code is in the public domain. I ran the test results, and there are no test failures. --- strstr