Re: [m68k] adjust some tests

[Daniel Jacobowitz <drow@false.org>]

On Mon, Jun 05, 2006 at 06:05:54PM +0100, Nathan Sidwell wrote:
> The asm-source tests are assembled using default options.  That defaults to 
> m68020 capabilities and the jbsr gets assembled to one of the bsr 
> instructions. However, using a 'jsr' directly in the source forces 
>  emission of a jsr, which is available on all m68k/cf cores, and allows the 
> resultant executable to be run on any of them.  The asm-source tests don't 
> pay attention to any multilib or compiler specific flags so I can't see a 
> way to specify to the assembler what the target cpu really is.
> 
> I suppose it would be possible to assemble and link the sources with gcc's 
> --no-startfiles --no-stdlib options.  That would allow this test to work 
> with multilibs, pass the right options from cflags, and avoid the need for 
> a fully specified path for any linker script that is needed.  However it 
> would tie the gdb testsuite to gcc.  Although I guess this test could probe 
> the compiler and discover whether it was gcc or not, and do the above if it 
> was or fall back on the old behaviour if it wasn't.  would something like 
> that be acceptable?

We've been back and forth around this many times, see most recently
revision 1.48 of asm-source.exp.  Let's not go around it again.  I
think there was some problem with using those options.

But it's supposed to skip the entire test if there's any multilib
flags; so if you're generating binaries you can't run, I wonder if
you've got the defaults messed up somehow?

-- 
Daniel Jacobowitz
CodeSourcery