public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "howarth at nitro dot med dot uc dot edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/33300] [libstdc++-v3] 27_io/ios_base/storage/2.cc with -m64 kills Darwin Date: Fri, 19 Dec 2008 14:05:00 -0000 [thread overview] Message-ID: <20081219140414.24999.qmail@sourceware.org> (raw) In-Reply-To: <bug-33300-12313@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from howarth at nitro dot med dot uc dot edu 2008-12-19 14:04 ------- I noticed today that r142822 no longer exhibited the failure of libstdc++-v3/testsuite/27_io/ios_base/storage/2.cc as... WARNING: program timed out. FAIL: 27_io/ios_base/storage/2.cc execution test at -m64 on i686-apple-darwin9 as it has up to as recently as r142799. So either the bug went latent or it was fixed by a patch in that range. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33300
next prev parent reply other threads:[~2008-12-19 14:05 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-09-04 9:48 [Bug testsuite/33300] New: " dominiq at lps dot ens dot fr 2008-12-19 14:05 ` howarth at nitro dot med dot uc dot edu [this message] 2009-02-09 20:53 ` [Bug testsuite/33300] " janis at gcc dot gnu dot org 2009-02-11 13:16 ` dominiq at lps dot ens dot fr
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=20081219140414.24999.qmail@sourceware.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).