Re: [PATCH] Update testsuite mechanism to allow object files as source files.

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

* Caroline Tice via Gdb-patches <gdb-patches@sourceware.org> [2020-07-16 11:13:24 -0700]:

> On Thu, Jul 16, 2020 at 10:33 AM Joseph Myers <joseph@codesourcery.com> wrote:
> >
> > On Thu, 16 Jul 2020, Caroline Tice via Gdb-patches wrote:
> >
> > > High level summary:
> > > In some (hopefully rare) cases, certain tests MUST be built with a
> > > particular compiler to work.  If that compiler is not GCC, then it
> > > makes it very burdensome for developers to run the GDB testsuite and
> > > test those tests.  This change allows those tests to use object files
> > > (generated by the required compiler) as the test source file, so that
> > > when the test suite is run with GCC those tests will still
> > > execute/test properly.
> >
> > How is this expected to work when the GDB being tested is configured for a
> > different architecture or OS from that of the checked-in object file and
> > may not be able to read its object file format at all?  Will all such
> > tests have explicit conditioning on the target for which GDB is
> > configured?
> 
> That is a very good point; I suppose this test should be marked to
> only work on the architecture for which the test was compiled? (I know
> I've seen those kinds of restrictions in testsuites before, although
> I'm not sure if the GDB testsuite is currently set up for such
> restrictions).

Yes tests can be restricted for particular architectures, look for
istarget checks throughout the testsuite, for example in:

  gdb/testsuite/gdb.arch/amd64-entry-value-param-dwarf5.exp

Thanks,
Andrew