Re: Copyright status gdb.fortran/vla-stride.exp test-case

[Andrew Burgess <andrew.burgess@embecosm.com>]

* Tom de Vries <tdevries@suse.de> [2020-08-18 11:50:29 +0200]:

> On 8/6/20 3:35 PM, Andrew Burgess wrote:
> > * Tom de Vries <tdevries@suse.de> [2020-08-06 12:41:36 +0200]:
> > 
> >> [ was: Re: [PUSHED] gdb/fortran: Support negative array stride in one
> >> limited case ]
> >>
> >> On 2/25/20 5:35 PM, Andrew Burgess wrote:
> >>> This issue was identified on the mailing list by Sergio:
> >>>
> >>>   https://sourceware.org/ml/gdb-patches/2020-01/msg00360.html
> >>>
> >>> The test for this issue is a new one written by me as the copyright
> >>> status of the original test is currently unknown.
> >>
> >> I just ran that test-case on master, and it passes, so it could be
> >> committed from that point of view.
> >>
> >> I've tracked down the test-case to commit 4efec01384 "vla: add stride
> >> support to fortran arrays." on user branch
> >> origin/users/bheckel/fortran-strides :
> >> ...
> >> commit 4efec01384648183cff07a8d6f050e47074ecfcd
> >> Author: Keven Boell <keven.boell@intel.com>
> >> Date:   Wed May 28 14:44:11 2014 +0100
> >>
> >>     vla: add stride support to fortran arrays.
> >>
> >>     2014-05-28  Bernhard Heckel  <bernhard.heckel@intel.com>
> >>                 Sanimir Agovic  <sanimir.agovic@intel.com>
> >>                 Keven Boell  <keven.boell@intel.com>
> >> ...
> >>
> >> It's not clear from the patch who contributed to the test-case.
> >>
> >> Bernard Heckel is listed in MAINTAINERS, the others not, but they are
> >> listed in both gdb and gdb/testsuite ChangeLogs.
> >>
> >> That's as far as I can take it.  Perhaps someone can look up the
> >> copyright assignment status.
> > 
> > I'm confused.  I thought the new test I wrote covered the issues
> > Sergio raised.
> 
> Right, I'm not questioning that.
> 
> > Is there some case that Bernard's test covers that is
> > not already covered by the existing Fortran tests?
> 
> I don't know.  I assumed that your test covered the problem that was
> reported, but not necessarily the whole test in which the problem was found.
> 
> >  What's the
> > motivation for tracking down the copyright status for this test?
> 
> It's part of the fedora patches for gdb, and there is an ongoing effort
> to move those to upstream gdb.  And I found that the test-case passed on
> trunk, so that looked easy.

Thanks.  With this explanation everything becomes much clearer.

Andrew