Re: [PATCH] Add alpha target to asm-source.exp test

[George France <france at handhelds dot org>]

Hello Michael,

I was in a rush last week when I sent the e-mail and I was not very clear.  
Let me try again.  

I know that stabs is broken on alpha.  My question is more of a QA question.  
Should the testsuite rely on the default configuration of the system that 
the test is being ran upon????  I believe that relying upon the default 
configuration produces inconsistent testsuite results. 

Shouldn't stabs and dwarf2 be tested on all the architectures????   This 
would create consistent testsuite results.  In the case of stabs on alpha, 
since we know that it is broken, the result that I would expect is XFAIL.

I will not have time to write a patch that would test both stabs and dwarf2 
for at least a week, but I would like to solve this problem and have 
consistent testsuite results.

I hope this clarifies things.

Best Regards,


--George


On Friday 08 February 2002 13:36, Michael Snyder wrote:
> Daniel Jacobowitz wrote:
> > On Thu, Feb 07, 2002 at 06:10:34PM -0500, George France wrote:
> > > Hello Priya,
> > >
> > > I like your patch. It makes sense to me,  but I have one question, in
> > > the code below.  You are setting the asm-flags to '-gdwaft2'.  I would
> > > assume that this is because '-g' is broken????  If '-g' is broken,
> > > shouldn't this be two tests???  One with '-g'. One with '-gdwarf2'.
> >
> > There's no point in testing -g on Alpha; -g defaults to stabs, and
> > stabs have never worked on 64-bit systems.
>
> -g defaults to whatever it's configured to default to.
> If alpha is 64 bit, then alpha should be configured to
> default to dwarf-2.