public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/11346] New: Regressions from 3.3.0 Date: Fri, 27 Jun 2003 09:26:00 -0000 [thread overview] Message-ID: <20030627092629.11346.ebotcazou@gcc.gnu.org> (raw) PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11346 Summary: Regressions from 3.3.0 Product: gcc Version: 3.3.1 Status: UNCONFIRMED Severity: critical Priority: P1 Component: libstdc++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: ebotcazou at gcc dot gnu dot org CC: gcc-bugs at gcc dot gnu dot org GCC build triplet: sparc*-sun-solaris2.* GCC host triplet: sparc*-sun-solaris2.* GCC target triplet: sparc*-sun-solaris2.* Two regressions have appeared between 06/14 and 06/26: FAIL: 22_locale/codecvt/max_length/char/wrapped_env.cc execution test FAIL: 22_locale/codecvt/max_length/char/wrapped_locale.cc execution test The log file doesn't contain any more detailed information.
next reply other threads:[~2003-06-27 9:26 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-06-27 9:26 ebotcazou at gcc dot gnu dot org [this message] 2003-06-27 14:24 ` [Bug libstdc++/11346] " bangerth at dealii dot org 2003-07-25 0:32 ` pme at gcc dot gnu dot org
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=20030627092629.11346.ebotcazou@gcc.gnu.org \ --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).