public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/39215] Running Testsuite with Multilib Flags exposes many errors in Testsuite (and gcc) Date: Mon, 18 Jul 2011 16:36:00 -0000 [thread overview] Message-ID: <bug-39215-4-e4glq47uaW@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-39215-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39215 Rainer Orth <ro at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |FIXED --- Comment #3 from Rainer Orth <ro at gcc dot gnu.org> 2011-07-18 16:34:28 UTC --- Solaris/x86 testresults are practically clean these days, for both multilibs and both 32-bit default and 64-bit default configurations.
next parent reply other threads:[~2011-07-18 16:36 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-39215-4@http.gcc.gnu.org/bugzilla/> 2011-07-18 16:36 ` ro at gcc dot gnu.org [this message] 2009-02-17 16:22 [Bug testsuite/39215] New: " rob1weld at aol dot com 2009-02-22 1:27 ` [Bug testsuite/39215] " rob1weld at aol dot com 2010-04-28 19:40 ` ro 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=bug-39215-4-e4glq47uaW@http.gcc.gnu.org/bugzilla/ \ --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).