C++ ABI testing issues, gcc-3.3 <-> gcc-3.2 compatibility

[Andreas Jaeger]

Nathan Sidwell <nathan@acm.org> writes:

> Daniel Berlin wrote:
>> 
>> > |> > That's the same result as given on IA-32 or IA-64, but those
>> > |> > tests are
>> > |> > #if !defined __i386__ && !defined __ia64__
>> > |> > Guess at least __alpha__ is a good candidate for this treatment too.
>> > |>
>> > |> x86-64 has the same problem, everything passes except bitfield3 (this
>> > |> is with GCC 3.2 plus some extra patches),
>> >
>> > Same on s390x.  Are there any platforms where it *does* pass?
>> I could swear I ran these tests on x86 or powerpc (can't remember which)
>> when it was first released by Intel, and everything passed.
> ditto, and the same this morning with the 3.2 branch. I'm confused.

The problem that I had is that config.mk has:

ifeq ($(shell uname -m),ia64)
        CXX=ecpc
        RUN=
        TOUCH=touch
        LIB=<enter complete library path name>
else
        CXX=g++
        RUN=:
        TOUCH=:
        LIB=<enter complete library path name>
endif

You need to change RUN and TOUCH also (same as ia64 case) - something
I didn't do and therefore everything worked for me since in this case
only compilation is done but no test is executed.

It might be that you made the same error I did, could you double
check, please?

Andreas
-- 
 Andreas Jaeger
  SuSE Labs aj@suse.de
   private aj@arthur.inka.de
    http://www.suse.de/~aj