Re: [PATCH][Middle-end]patch for fixing PR 86519

On 08/23/2018 10:13 AM, Qing Zhao wrote: > >> On Aug 22, 2018, at 5:01 PM, Jeff Law wrote: >> >> On 08/22/2018 11:05 AM, Qing Zhao wrote: >>> On Aug 22, 2018, at 10:50 AM, Rainer Orth wrote: Hi Qing, > From the comments you put into PR86519, for SPARC, looks like

Re: [PATCH][Middle-end]patch for fixing PR 86519

> On Aug 22, 2018, at 5:01 PM, Jeff Law wrote: > > On 08/22/2018 11:05 AM, Qing Zhao wrote: >> >>> On Aug 22, 2018, at 10:50 AM, Rainer Orth >>> wrote: >>> >>> Hi Qing, >>> From the comments you put into PR86519, for SPARC, looks like that only 32-bit sparc has the problem.

Re: [PATCH][Middle-end]patch for fixing PR 86519

On 08/22/2018 11:05 AM, Qing Zhao wrote: > >> On Aug 22, 2018, at 10:50 AM, Rainer Orth >> wrote: >> >> Hi Qing, >> >>> From the comments you put into PR86519, for SPARC, looks like that only >>> 32-bit sparc has the problem. >>> sparcv9 does NOT have the same issue. >>> >>> I was trying to

Re: [PATCH][Middle-end]patch for fixing PR 86519

> On Aug 22, 2018, at 10:50 AM, Rainer Orth > wrote: > > Hi Qing, > >> From the comments you put into PR86519, for SPARC, looks like that only >> 32-bit sparc has the problem. >> sparcv9 does NOT have the same issue. >> >> I was trying to find the string to represent 32-bit sparc target,

Re: [PATCH][Middle-end]patch for fixing PR 86519

Hi Qing, > From the comments you put into PR86519, for SPARC, looks like that only > 32-bit sparc has the problem. > sparcv9 does NOT have the same issue. > > I was trying to find the string to represent 32-bit sparc target, but > haven’t found it. > > my guess is: sparc32*-*-*, is this

Re: [PATCH][Middle-end]patch for fixing PR 86519

Hi, Rainer, >From the comments you put into PR86519, for SPARC, looks like that only 32-bit >sparc has the problem. sparcv9 does NOT have the same issue. I was trying to find the string to represent 32-bit sparc target, but haven’t found it. my guess is: sparc32*-*-*, is this correct?

Re: [PATCH][Middle-end]patch for fixing PR 86519

thanks. now, I can repeat the failure. Qing > On Aug 21, 2018, at 7:25 PM, Paul Hua wrote: > > On Wed, Aug 22, 2018 at 2:15 AM Qing Zhao > wrote: >> >> >>> On Aug 21, 2018, at 8:07 AM, Paul Hua wrote: >>> >>> Hi, Qing, >>> >>> The cfarm machine gcc23 can build

Re: [PATCH][Middle-end]patch for fixing PR 86519

On Wed, Aug 22, 2018 at 2:15 AM Qing Zhao wrote: > > > > On Aug 21, 2018, at 8:07 AM, Paul Hua wrote: > > > > Hi, Qing, > > > > The cfarm machine gcc23 can build mips64el successful, configure with > > "../configure --prefix=/opt/gcc-9 MISSING=texinfo MAKEINFO=missing > >

Re: [PATCH][Middle-end]patch for fixing PR 86519

Hi, Qing, The cfarm machine gcc23 can build mips64el successful, configure with "../configure --prefix=/opt/gcc-9 MISSING=texinfo MAKEINFO=missing --target=mips64el-linux-gnu --enable-languages=c,c++ On Tue, Aug 21, 2018 at 7:02 AM Qing Zhao wrote: > > Hi, Paul, > > I was trying to repeat this

Re: [PATCH][Middle-end]patch for fixing PR 86519

Hi, Paul, I was trying to repeat this issue on a mips machine today, but failed… the only mips machines I can access are those in gcc compile farm, I chose gcc22, but failed to build GCC on this machine. do you know any other machine in gcc compile farm that can repeat this issue? thanks a

Re: [PATCH][Middle-end]patch for fixing PR 86519

Hi, Rainer, thanks a lot to report the issues with mips and sparc platform. Yes, looks like even on the assembly level, the string scanning still not reliable on different platforms. I agree with Jeff’s suggestion to apply different search result for different platforms. I will update the

Re: [PATCH][Middle-end]patch for fixing PR 86519

Hi Jeff, > On 08/17/2018 09:43 PM, Paul Hua wrote: >> Hi Qing: >> >>> >>> the change has been committed as: >>> https://gcc.gnu.org/viewcvs/gcc?view=revision=263563 >>> >>> >>> Qing >>> >> >> The strcmpopt_6.c test still fails on mips64el

Re: [PATCH][Middle-end]patch for fixing PR 86519

On 08/17/2018 09:43 PM, Paul Hua wrote: > Hi Qing: > >> >> the change has been committed as: >> https://gcc.gnu.org/viewcvs/gcc?view=revision=263563 >> >> >> Qing >> > > The strcmpopt_6.c test still fails on mips64el target. > >

Re: [PATCH][Middle-end]patch for fixing PR 86519

Hi Qing: > > the change has been committed as: > https://gcc.gnu.org/viewcvs/gcc?view=revision=263563 > > > Qing > The strcmpopt_6.c test still fails on mips64el target. gcc.dg/strcmpopt_6.c: memcmp found 4 times FAIL: gcc.dg/strcmpopt_6.c

Re: [PATCH][Middle-end]patch for fixing PR 86519

> On Aug 14, 2018, at 11:25 PM, Jeff Law wrote: > > On 08/14/2018 08:57 AM, Qing Zhao wrote: >> Hi, >> >> PR 86519:New test case gcc.dg/strcmpopt_6.c fails with its introduction in >> r262636. >> >> gcc/ChangeLog: >> >> +2018-08-14 Qing Zhao >> + >> + PR testsuite/86519 >> +

Re: [PATCH][Middle-end]patch for fixing PR 86519

On 08/14/2018 08:57 AM, Qing Zhao wrote: > Hi, > > PR 86519:New test case gcc.dg/strcmpopt_6.c fails with its introduction in > r262636. > > ***the root cause is: > > for the following call to memcmp: __builtin_memcmp (s->s, "a", 3); > the specified length 3 is larger than the length of "a",