public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "wanderer at rsu dot ru" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/19656] New: libstdc++ testsuite results differ if bootstrap gcc 4.0 using some gcc 4.0 version or early (gcc 3.4.3) gcc version at FreeBSD Date: Thu, 27 Jan 2005 13:00:00 -0000 [thread overview] Message-ID: <20050127125831.19656.wanderer@rsu.ru> (raw) If i bootstrap using installed some old or same CVS mainline gcc (a.k.a. gcc 4.0.0) i have in testsuit results: === libstdc++ Summary === # of expected passes 3472 # of unexpected failures 1 # of unexpected successes 1 # of expected failures 5 If i bootstrap using gcc 3.4.3 version i have in testsuit results: === libstdc++ Summary === # of expected passes 3454 # of unexpected failures 10 # of unexpected successes 1 # of expected failures 5 contrib/compare_tests output: Tests that now fail, but worked before: 22_locale/collate/compare/wchar_t/2.cc (test for excess errors) 22_locale/collate/compare/wchar_t/wrapped_env.cc (test for excess errors) 22_locale/collate/compare/wchar_t/wrapped_locale.cc (test for excess errors) 22_locale/collate/hash/wchar_t/2.cc (test for excess errors) 22_locale/collate/hash/wchar_t/wrapped_env.cc (test for excess errors) 22_locale/collate/hash/wchar_t/wrapped_locale.cc (test for excess errors) 22_locale/collate/transform/wchar_t/2.cc (test for excess errors) 22_locale/collate/transform/wchar_t/wrapped_env.cc (test for excess errors) 22_locale/collate/transform/wchar_t/wrapped_locale.cc (test for excess errors) Old tests that passed, that have disappeared: (Eeek!) 22_locale/collate/compare/wchar_t/2.cc execution test 22_locale/collate/compare/wchar_t/wrapped_env.cc execution test 22_locale/collate/compare/wchar_t/wrapped_locale.cc execution test 22_locale/collate/hash/wchar_t/2.cc execution test 22_locale/collate/hash/wchar_t/wrapped_env.cc execution test 22_locale/collate/hash/wchar_t/wrapped_locale.cc execution test 22_locale/collate/transform/wchar_t/2.cc execution test 22_locale/collate/transform/wchar_t/wrapped_env.cc execution test 22_locale/collate/transform/wchar_t/wrapped_locale.cc execution test I have all *.sum and *.log files from both tastsuite runs and can post its if requared -- Summary: libstdc++ testsuite results differ if bootstrap gcc 4.0 using some gcc 4.0 version or early (gcc 3.4.3) gcc version at FreeBSD Product: gcc Version: 4.0.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: libstdc++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: wanderer at rsu dot ru CC: gcc-bugs at gcc dot gnu dot org GCC build triplet: i386-unknown-freebsd5.3 GCC host triplet: i386-unknown-freebsd5.3 GCC target triplet: i386-unknown-freebsd5.3 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19656
next reply other threads:[~2005-01-27 13:00 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-01-27 13:00 wanderer at rsu dot ru [this message] 2005-01-27 13:04 ` [Bug libstdc++/19656] " wanderer at rsu dot ru 2005-01-27 13:09 ` wanderer at rsu dot ru 2005-01-27 13:25 ` pinskia at gcc dot gnu dot org 2005-01-28 23:33 ` ljrittle at gcc dot gnu dot org 2005-01-29 0:04 ` wanderer at rsu dot ru 2005-01-29 23:49 ` wanderer at rsu dot ru 2005-01-31 15:05 ` wanderer at rsu dot ru 2005-01-31 16:59 ` wanderer at rsu dot ru 2005-01-31 18:45 ` wanderer at rsu dot ru 2005-02-21 21:28 ` wanderer at rsu dot ru
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20050127125831.19656.wanderer@rsu.ru \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).