public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl at lucon dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/25741] Gcc testsuite isn't parallel build safe Date: Tue, 10 Jan 2006 20:20:00 -0000 [thread overview] Message-ID: <20060110202001.28747.qmail@sourceware.org> (raw) In-Reply-To: <bug-25741-682@http.gcc.gnu.org/bugzilla/> ------- Comment #4 from hjl at lucon dot org 2006-01-10 20:20 ------- Created an attachment (id=10608) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=10608&action=view) List of tests with the same prefix This is a list of ests with the same prefix. There are quite a few. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25741
next prev parent reply other threads:[~2006-01-10 20:20 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-01-10 16:03 [Bug testsuite/25741] New: " hjl at lucon dot org 2006-01-10 17:25 ` [Bug testsuite/25741] " steven at gcc dot gnu dot org 2006-01-10 19:06 ` hjl at lucon dot org 2006-01-10 19:22 ` hjl at lucon dot org 2006-01-10 20:20 ` hjl at lucon dot org [this message] 2006-01-16 21:43 ` hjl at gcc dot gnu dot org 2006-01-29 20:09 ` pinskia at gcc dot gnu dot org 2006-03-31 17:36 ` hjl at gcc dot gnu dot org 2006-03-31 17:42 ` hjl at gcc dot gnu dot org 2006-03-31 21:39 ` pinskia 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=20060110202001.28747.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).