RFC: xfail 20020227-1.c on 64-bit targets, how to catch -m64 in dejagnu?

[Kaveh R. Ghazi]

 > From: Hans-Peter Nilsson <hp@bitrange.com>
 > 
 > On Wed, 24 Apr 2002, Kaveh R. Ghazi wrote:
 > 
 > > # This test reportedly fails on all 64-bit targets, see PR6221.  It's
 > > # been observed to fail on at least mips-irix6, alpha, ia64, hppa64,
 > > # and sparc64/sparcv9 during April 2002.
 > >
 > > global target_triplet
 > > if { [istarget "*64*-*-*"] || [istarget "sparcv9-*-*"]
 > >      || [istarget "alpha*-*-*"] || [istarget "mips*-*-irix6*"]
 > >      || [string match "*-m64*" "$CFLAGS"] } {
 > 
 > Hey, you forgot mmix-knuth-mmixware, where the bug was spotted
 > (see the test)!

I did see that, but the way its written in past tense "This testcase
failed on mmix-knuth-mmixware" lead me to believe it used to fail and
was fixed.  I guess not, so I'll include it.


 > >     set torture_execute_xfail "$target_triplet"
 > 
 > Use "set torture_execute_xfail [istarget]", so you don't need
 > global target_triplet.
 > brgds, H-P

Ok, but is doing that somehow better or just different?
(I'm no expert at this stuff so I'm curious.)

What's so bad about global that we'd call a proc which just returns
the same global value?

		--Kaveh
--
Kaveh R. Ghazi			Director of Systems Architecture
ghazi@caip.rutgers.edu		Qwest Global Services