This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
RE: [patch] cilkplus array notation for C (clean, independent patchset, take 1)
- From: "Iyer, Balaji V" <balaji dot v dot iyer at intel dot com>
- To: Aldy Hernandez <aldyh at redhat dot com>
- Cc: Jakub Jelinek <jakub at redhat dot com>, Jeff Law <law at redhat dot com>, "Joseph S. Myers" <joseph at codesourcery dot com>, gcc-patches <gcc-patches at gcc dot gnu dot org>
- Date: Thu, 21 Mar 2013 13:15:41 +0000
- Subject: RE: [patch] cilkplus array notation for C (clean, independent patchset, take 1)
- References: <5149D62F dot 9070503 at redhat dot com> <5149E4C7 dot 1090206 at redhat dot com> <514A9B12 dot 8050502 at redhat dot com> <20130321060933 dot GQ12913 at tucnak dot redhat dot com> <514B0485 dot 8050300 at redhat dot com> <BF230D13CA30DD48930C31D40993300016D7D9BB at FMSMSX102 dot amr dot corp dot intel dot com> <514B0657 dot 3090802 at redhat dot com>
> -----Original Message-----
> From: Aldy Hernandez [mailto:aldyh@redhat.com]
> Sent: Thursday, March 21, 2013 9:09 AM
> To: Iyer, Balaji V
> Cc: Jakub Jelinek; Jeff Law; Joseph S. Myers; gcc-patches
> Subject: Re: [patch] cilkplus array notation for C (clean, independent patchset,
> take 1)
>
> On 03/21/13 08:06, Iyer, Balaji V wrote:
> >>
> >> Balaji, please check the corresponding .sum files before and after
> >> your patch to make sure that the same number of tests are being
> >> tested. We have a nifty script in contrib/compare_tests for this task.
> >
> > That's how I verify it. (I grep for the ^FAIL in trunk and the applied branch and
> make sure the output files are the same by going through it). Did I miss
> anything?
>
> If you're using compare_tests, you should be fine. But just grepping for FAIL
> won't do because there are tests that could have passed before, but are no
> longer being tested, so they don't show up as a fail. I believe compare_tests
> complains with "tests that used to pass but have disappeared" (or something
> similar).
I first look at the expected passes, expected fails, etc. If those numbers match up, then I do what I said above . Otherwise I look at things that have failed that shouldn't and/or passed that shouldn't have (this, should almost never happen because all the Cilk plus related code are all enclosed between inside an if (flag_enable_cilkplus) statement).
>
> >
> >>
> >> And as Jakub has said, check (with and) without parallelization.
> >>
> >
> > Yes, I am doing that also for the patch I am submitting.
>
> Thank you.
- References:
- [patch] cilkplus array notation for C (clean, independent patchset, take 1)
- Re: [patch] cilkplus array notation for C (clean, independent patchset, take 1)
- Re: [patch] cilkplus array notation for C (clean, independent patchset, take 1)
- Re: [patch] cilkplus array notation for C (clean, independent patchset, take 1)
- Re: [patch] cilkplus array notation for C (clean, independent patchset, take 1)
- RE: [patch] cilkplus array notation for C (clean, independent patchset, take 1)
- Re: [patch] cilkplus array notation for C (clean, independent patchset, take 1)