John David Anglin writes:
> > While preparing gcc-3.1 packages I noticed many eh-related regressions
> > fixed in the trunk, when dwarf2 support was added. With Dave's
> > guidance I made a diff of the pa subdirectory from the trunk and
> > applied it to the branch. Although many FAILS are gone, there are some
> > new (diff below).
>
> In general, option b has much better c++ results than a). The c++
> test results are essentially identical to those with 3.2. However,
> compared to the results that I have been posting for 3.2, we have
> the following new failures:
>
> gcc.c-torture/execute/ieee/rbug.c
>
> g77.f-torture/execute/19990313-[0-3].f
>
> 20_util/allocator_members.cc execution test
> 22_locale/codecvt_members_char_char.cc execution test
> 22_locale/codecvt_members_wchar_t_char.cc execution test
> 22_locale/ctor_copy_dtor.cc execution test
> 22_locale/ctype_members_wchar_t.cc execution test
> 27_io/ostream_inserter_arith.cc execution test
the libstdc failures are no regressions compared to a (3.1).
> It would probably be useful to compare test results for b and c. It may
> be that some of the above are glibc or system problems.
this is a diff of the test results for b and c. g++ is worse, the
regressions for g77 and gcc are new test cases in the trunk. One new
gcc regression:
FAIL: gcc.c-torture/compile/20000504-1.c, -O1
--- ../../3.1/tr/test-summary Fri May 3 12:51:46 2002
+++ test-summary Sun May 5 13:59:34 2002
@@ -1,11 +1,15 @@
-LAST_UPDATED: Thu May 2 21:54:20 UTC 2002
-
+LAST_UPDATED:
Native configuration is hppa-unknown-linux-gnu
=== g++ tests ===
Running target unix
+FAIL: g++.dg/template/friend6.C (test for excess errors)
+FAIL: g++.dg/template/typename2.C (test for excess errors)
+FAIL: g++.dg/warn/Wunused-2.C (test for warnings, line 5)
+FAIL: g++.dg/warn/effc1.C (test for warnings, line 13)
+FAIL: g++.dg/warn/effc1.C (test for excess errors)
FAIL: g++.brendan/new3.C Execution test
FAIL: g++.law/profile1.C (test for excess errors)
XPASS: g++.mike/eh33.C (test for excess errors)
@@ -16,70 +20,55 @@
=== g++ Summary ===
-# of expected passes 7155
-# of unexpected failures 2
+# of expected passes 7252
+# of unexpected failures 7
# of unexpected successes 5
-# of expected failures 87
+# of expected failures 86
# of untested testcases 23
# of unsupported tests 4
-/home/packages/gcc/3.1/gcc-3.1-3.1ds0/build/gcc/testsuite/../g++ version 3.1
20020502 (Debian prerelease)
+/home/packages/gcc/try/gcc-3.1-3.1ds90/build/gcc/testsuite/../g++ version 3.1
20020429 (Debian experimental)
=== g77 tests ===
Running target unix
-FAIL: g77.f-torture/execute/19990313-0.f execution, -O0
-FAIL: g77.f-torture/execute/19990313-0.f execution, -O1
-FAIL: g77.f-torture/execute/19990313-0.f execution, -O2
-FAIL: g77.f-torture/execute/19990313-0.f execution, -O3 -fomit-frame-pointer
-FAIL: g77.f-torture/execute/19990313-0.f execution, -O3 -g
-FAIL: g77.f-torture/execute/19990313-0.f execution, -Os
-FAIL: g77.f-torture/execute/19990313-1.f execution, -O0
-FAIL: g77.f-torture/execute/19990313-1.f execution, -O1
-FAIL: g77.f-torture/execute/19990313-1.f execution, -O2
-FAIL: g77.f-torture/execute/19990313-1.f execution, -O3 -fomit-frame-pointer
-FAIL: g77.f-torture/execute/19990313-1.f execution, -O3 -g
-FAIL: g77.f-torture/execute/19990313-1.f execution, -Os
-FAIL: g77.f-torture/execute/19990313-2.f execution, -O0
-FAIL: g77.f-torture/execute/19990313-2.f execution, -O1
-FAIL: g77.f-torture/execute/19990313-2.f execution, -O2
-FAIL: g77.f-torture/execute/19990313-2.f execution, -O3 -fomit-frame-pointer
-FAIL: g77.f-torture/execute/19990313-2.f execution, -O3 -g
-FAIL: g77.f-torture/execute/19990313-2.f execution, -Os
-FAIL: g77.f-torture/execute/19990313-3.f execution, -O0
-FAIL: g77.f-torture/execute/19990313-3.f execution, -O1
-FAIL: g77.f-torture/execute/19990313-3.f execution, -O2
-FAIL: g77.f-torture/execute/19990313-3.f execution, -O3 -fomit-frame-pointer
-FAIL: g77.f-torture/execute/19990313-3.f execution, -O3 -g
-FAIL: g77.f-torture/execute/19990313-3.f execution, -Os
+FAIL: g77.f-torture/execute/6367.f execution, -O0
+FAIL: g77.f-torture/execute/6367.f execution, -O1
+FAIL: g77.f-torture/execute/6367.f execution, -O2
+FAIL: g77.f-torture/execute/6367.f execution, -O3 -fomit-frame-pointer
+FAIL: g77.f-torture/execute/6367.f execution, -O3 -fomit-frame-pointer
-funroll-loops
+FAIL: g77.f-torture/execute/6367.f execution, -O3 -fomit-frame-pointer
-funroll-all-loops -finline-functions
+FAIL: g77.f-torture/execute/6367.f execution, -O3 -g
+FAIL: g77.f-torture/execute/6367.f execution, -Os
=== g77 Summary ===
-# of expected passes 1428
-# of unexpected failures 24
+# of expected passes 1618
+# of unexpected failures 8
# of unsupported tests 8
-/home/packages/gcc/3.1/gcc-3.1-3.1ds0/build/gcc/testsuite/../g77 version 3.1
20020502 (Debian prerelease)
+/home/packages/gcc/try/gcc-3.1-3.1ds90/build/gcc/testsuite/../g77 version 3.1
20020429 (Debian experimental)
=== gcc tests ===
Running target unix
-FAIL: gcc.c-torture/execute/20020307-2.c compilation, -O0
-UNRESOLVED: gcc.c-torture/execute/20020307-2.c execution, -O0
-FAIL: gcc.c-torture/execute/20020307-2.c compilation, -O1
-UNRESOLVED: gcc.c-torture/execute/20020307-2.c execution, -O1
-FAIL: gcc.c-torture/execute/20020307-2.c compilation, -O2
-UNRESOLVED: gcc.c-torture/execute/20020307-2.c execution, -O2
-FAIL: gcc.c-torture/execute/20020307-2.c compilation, -O3
-fomit-frame-pointer
-UNRESOLVED: gcc.c-torture/execute/20020307-2.c execution, -O3
-fomit-frame-pointer
-FAIL: gcc.c-torture/execute/20020307-2.c compilation, -O3
-fomit-frame-pointer -funroll-loops
-UNRESOLVED: gcc.c-torture/execute/20020307-2.c execution, -O3
-fomit-frame-pointer -funroll-loops
-FAIL: gcc.c-torture/execute/20020307-2.c compilation, -O3
-fomit-frame-pointer -funroll-all-loops -finline-functions
-UNRESOLVED: gcc.c-torture/execute/20020307-2.c execution, -O3
-fomit-frame-pointer -funroll-all-loops -finline-functions
-FAIL: gcc.c-torture/execute/20020307-2.c compilation, -O3 -g
-UNRESOLVED: gcc.c-torture/execute/20020307-2.c execution, -O3 -g
-FAIL: gcc.c-torture/execute/20020307-2.c compilation, -Os
-UNRESOLVED: gcc.c-torture/execute/20020307-2.c execution, -Os
+FAIL: gcc.c-torture/compile/20000504-1.c, -O1
+FAIL: gcc.c-torture/execute/20020412-1.c compilation, -O0
+UNRESOLVED: gcc.c-torture/execute/20020412-1.c execution, -O0
+FAIL: gcc.c-torture/execute/20020412-1.c compilation, -O1
+UNRESOLVED: gcc.c-torture/execute/20020412-1.c execution, -O1
+FAIL: gcc.c-torture/execute/20020412-1.c compilation, -O2
+UNRESOLVED: gcc.c-torture/execute/20020412-1.c execution, -O2
+FAIL: gcc.c-torture/execute/20020412-1.c compilation, -O3
-fomit-frame-pointer
+UNRESOLVED: gcc.c-torture/execute/20020412-1.c execution, -O3
-fomit-frame-pointer
+FAIL: gcc.c-torture/execute/20020412-1.c compilation, -O3
-fomit-frame-pointer -funroll-loops
+UNRESOLVED: gcc.c-torture/execute/20020412-1.c execution, -O3
-fomit-frame-pointer -funroll-loops
+FAIL: gcc.c-torture/execute/20020412-1.c compilation, -O3
-fomit-frame-pointer -funroll-all-loops -finline-functions
+UNRESOLVED: gcc.c-torture/execute/20020412-1.c execution, -O3
-fomit-frame-pointer -funroll-all-loops -finline-functions
+FAIL: gcc.c-torture/execute/20020412-1.c compilation, -O3 -g
+UNRESOLVED: gcc.c-torture/execute/20020412-1.c execution, -O3 -g
+FAIL: gcc.c-torture/execute/20020412-1.c compilation, -Os
+UNRESOLVED: gcc.c-torture/execute/20020412-1.c execution, -Os
FAIL: gcc.c-torture/execute/va-arg-22.c execution, -O0
FAIL: gcc.c-torture/execute/va-arg-22.c execution, -O1
FAIL: gcc.c-torture/execute/va-arg-22.c execution, -O2
@@ -88,20 +77,18 @@
FAIL: gcc.c-torture/execute/va-arg-22.c execution, -O3 -fomit-frame-pointer
-funroll-all-loops -finline-functions
FAIL: gcc.c-torture/execute/va-arg-22.c execution, -O3 -g
FAIL: gcc.c-torture/execute/va-arg-22.c execution, -Os
-FAIL: gcc.c-torture/execute/ieee/rbug.c execution, -O3 -fomit-frame-pointer
-FAIL: gcc.c-torture/execute/ieee/rbug.c execution, -O3 -g
FAIL: gcc.dg/20020312-2.c (test for excess errors)
WARNING: gcc.dg/20020312-2.c compilation failed to produce executable
FAIL: gcc.dg/asm-names.c (test for excess errors)
=== gcc Summary ===
-# of expected passes 18193
-# of unexpected failures 20
+# of expected passes 18395
+# of unexpected failures 19
# of expected failures 70
# of unresolved testcases 8
-# of unsupported tests 113
-/home/packages/gcc/3.1/gcc-3.1-3.1ds0/build/gcc/xgcc version 3.1 20020502
(Debian prerelease)
+# of unsupported tests 118
+/home/packages/gcc/try/gcc-3.1-3.1ds90/build/gcc/xgcc version 3.1 20020429
(Debian experimental)
=== objc tests ===
@@ -112,7 +99,7 @@
# of expected passes 1036
# of expected failures 6
-/home/packages/gcc/3.1/gcc-3.1-3.1ds0/build/gcc/xgcc version 3.1 20020502
(Debian prerelease)
+/home/packages/gcc/try/gcc-3.1-3.1ds90/build/gcc/xgcc version 3.1 20020429
(Debian experimental)
=== libstdc++-v3 tests ===
@@ -133,7 +120,7 @@
# of unexpected failures 8
# of expected failures 25
-Compiler version: 3.1 20020502 (Debian prerelease)
+Compiler version: 3.1 20020429 (Debian experimental)
Platform: hppa-unknown-linux-gnu
configure flags: --host=hppa-linux -v
--enable-languages=c,c++,f77,proto,objc,ada --prefix=/usr
--infodir='\${prefix}/share/info' --mandir=\${prefix}/share/man
--with-gxx-include-dir=/usr/include/g++-v3-3.1 --enable-shared --with-gnu-as
--with-gnu-ld --with-system-zlib --enable-long-long --enable-nls
--without-included-gettext --enable-clocale=gnu --enable-threads=posix
--with-cpp-install-dir=bin
BOOT_CFLAGS=-O2
> I am fairly
> certain c will build on all platforms. However, I know that there is
> one c regression under hppa near the beginning of march. There is another
> at the beginning of May.
Ada doesn't build:
../../xgcc -B../../ -c -g -O2 -g -O2 -W -Wall -gnatpg -I.
-I/home/packages/gcc/try/gcc-3.1-3.1ds90/src/gcc/ada s-taprop.adb
s-taprop.adb:48:12: warning: no entities of "Os_Primitives" are referenced
make[4]: *** [s-taprop.o] Error 1
make[4]: Leaving directory
`/home/packages/gcc/try/gcc-3.1-3.1ds90/build/gcc/ada/rts'
>
> As a matter of release philosophy, I don't much like hybrids. Option
> b adds another permutation to maintain even if the new c++ capabilities
> are very tempting. My focus will be 3.2. 3.1 will only get small bug
> fixes. If we keep to the main releases, it much easier to verify and
> resolve bugs.
Ok.
> So, I would say use a as the default. This is the conservative choice
> and well tested across a broad range of systems. Option a can easily be
> used to build c. Maybe you could include c as well for experimental
> development and building c++ packages that need the dw2 support under
> parisc-linux.
I'll keep building the snapshot package. maybe an alternative is to
build a gcc-3.2 package with incompatible sonames, so packages can be
easily identified. we had this situation before the gcc-3.0
release. Using the "300" names, then switching to upstream names,
before the final ABI for 3.0 was frozen.
MatthiasN…
[EMAIL PROTECTED]
隊[huæâjxi¥ªÞªç¬¶X¬¶Ç^n&§¢¸0ŠØZ²æãyËh~éì¹» ®&ÞNº.nW‚¢{ZrÙb²Ùš²×«–+-±×›‰©è®
