[v3] unify 3_4 and 3_5 libstdc++

Paolo Carlini pcarlini@suse.de
Tue Mar 16 19:23:00 GMT 2004


Hi,

Benjamin Kosnik wrote:

> This patch set unifies the libstdc++ ABI's across 3.4 and 3.5 trees. It
> does not break out bits into small chunks, and includes things like
> testsuite layout changes and documentation additions that are not
> strictly necessary from an ABI point of view but seem like things that
> will help long-term maintenance of the 3.4 tree going forward.

Thanks.

> The testresults from the current gcc-3_4-branch sources, with this patch
> applied, are fine on the two targets I have built: x86 linux (FC1) and
> powerpc darwin (10.3).

I have just finished regtesting on x86_64-linux and ia64-linux, a couple 
of pretty
up to date machines.

The results on x86-64 are pretty good:

Before
------
XPASS: 26_numerics/c99_classification_macros_c.cc (test for excess errors)
XPASS: 27_io/fpos/14320-1.cc execution test

                === libstdc++ Summary ===

# of expected passes            2573
# of unexpected successes       2
# of expected failures          4

After
-----
XPASS: 26_numerics/c99_classification_macros_c.cc (test for excess errors)
XPASS: 27_io/fpos/14320-1.cc execution test
FAIL: thread/pthread4.cc execution test
FAIL: thread/pthread7-rope.cc execution test

                === libstdc++ Summary ===

# of expected passes            2627
# of unexpected failures        2
# of unexpected successes       2
# of expected failures          4

however, a quick look to testresults too reveals that randomly some pthread
tests are failing.

Anyway, ia64 is quite problematic:

Before
------
XPASS: 26_numerics/c99_classification_macros_c.cc (test for excess errors)
XPASS: 27_io/fpos/14320-1.cc execution test

                === libstdc++ Summary ===

# of expected passes            2573
# of unexpected successes       2
# of expected failures          4

After
-----
14176.exe(4109): unaligned access to 0x6000000000004341, 
ip=0x4000000000001c20
14176.exe(4109): unaligned access to 0x6000000000004341, 
ip=0x4000000000001c30
14176.exe(4109): unaligned access to 0x6000000000004352, 
ip=0x4000000000001c20
14176.exe(4109): unaligned access to 0x6000000000004352, 
ip=0x4000000000001c30
binders.exe(4651): unaligned access to 0x6000000000004342, 
ip=0x4000000000001fd0
binders.exe(4651): unaligned access to 0x6000000000004342, 
ip=0x4000000000001fe0
binders.exe(4651): unaligned access to 0x6000000000004354, 
ip=0x4000000000001fd0
binders.exe(4651): unaligned access to 0x6000000000004354, 
ip=0x4000000000001fe0
FAIL: 22_locale/locale/cons/12658_thread.cc execution test
FAIL: 22_locale/messages/members/char/1.cc execution test
FAIL: 22_locale/messages/members/char/2.cc execution test
FAIL: 22_locale/messages/members/char/wrapped_env.cc execution test
FAIL: 22_locale/messages/members/char/wrapped_locale.cc execution test
FAIL: 22_locale/messages_byname/named_equivalence.cc execution test
7161.exe(1336): unaligned access to 0x6000000000008341, 
ip=0x4000000000002610
7161.exe(1336): unaligned access to 0x6000000000008341, 
ip=0x4000000000002620
7161.exe(1336): unaligned access to 0x6000000000008352, 
ip=0x4000000000002610
7161.exe(1336): unaligned access to 0x6000000000008352, 
ip=0x4000000000002620
2.exe(3743): unaligned access to 0x600000000000c341, ip=0x4000000000006a90
2.exe(3743): unaligned access to 0x600000000000c341, ip=0x4000000000006aa0
2.exe(3743): unaligned access to 0x600000000000c352, ip=0x4000000000006a90
2.exe(3743): unaligned access to 0x600000000000c352, ip=0x4000000000006aa0
1.exe(6750): unaligned access to 0x6000000000008344, ip=0x4000000000002a90
1.exe(6750): unaligned access to 0x6000000000008344, ip=0x4000000000002aa0
1.exe(6750): unaligned access to 0x600000000000836c, ip=0x4000000000002a90
1.exe(6750): unaligned access to 0x600000000000836c, ip=0x4000000000002aa0
iterator.exe(7621): unaligned access to 0x600000000000d654, 
ip=0x40000000000037c0
iterator.exe(7621): unaligned access to 0x600000000000d654, 
ip=0x40000000000037d0
iterator.exe(7621): unaligned access to 0x600000000000d67c, 
ip=0x40000000000037c0
iterator.exe(7621): unaligned access to 0x600000000000d67c, 
ip=0x40000000000037d0
rel_ops.exe(8240): unaligned access to 0x6000000000004344, 
ip=0x40000000000022f0
rel_ops.exe(8240): unaligned access to 0x6000000000004344, 
ip=0x4000000000002300
rel_ops.exe(8240): unaligned access to 0x600000000000436c, 
ip=0x40000000000022f0
rel_ops.exe(8240): unaligned access to 0x600000000000436c, 
ip=0x4000000000002300
XPASS: 26_numerics/c99_classification_macros_c.cc (test for excess errors)
XPASS: 27_io/fpos/14320-1.cc execution test
FAIL: thread/pthread7-rope.cc execution test

                === libstdc++ Summary ===

# of expected passes            2622
# of unexpected failures        7
# of unexpected successes       2
# of expected failures          4

In particular, this set of testcases is the very same that is failing
in mainline on sparc(64)-solaris (see Kaveh's results):

    20_util/allocator/14176.cc
    20_util/binders.cc
    23_containers/priority_queue/members/7161.cc
    23_containers/vector/cons/2.cc
    23_containers/vector/modifiers/1.cc
    24_iterators/iterator.cc
    24_iterators/rel_ops.cc

I'm now trying to isolate the problem, by varying the configure options.

The messages failures are pretty old, and often happen on x86_64 systems 
too.

That's all for now,
Paolo.



More information about the Libstdc++ mailing list