public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pcarlini at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/33612] make check -jN should fully use N cores
Date: Mon, 25 Feb 2008 18:10:00 -0000 [thread overview]
Message-ID: <20080225181016.31735.qmail@sourceware.org> (raw)
In-Reply-To: <bug-33612-365@http.gcc.gnu.org/bugzilla/>
------- Comment #3 from pcarlini at suse dot de 2008-02-25 18:10 -------
Eh! I think we should only double check that tests creating / writing files use
unique names...
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33612
next prev parent reply other threads:[~2008-02-25 18:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-01 18:21 [Bug libstdc++/33612] New: " bkoz at gcc dot gnu dot org
2007-10-01 18:21 ` [Bug libstdc++/33612] " bkoz at gcc dot gnu dot org
2007-10-01 18:30 ` pinskia at gcc dot gnu dot org
2008-02-25 17:29 ` bkoz at gcc dot gnu dot org
2008-02-25 18:10 ` pcarlini at suse dot de [this message]
2009-01-08 22:47 ` bkoz at gcc dot gnu dot org
[not found] <bug-33612-4@http.gcc.gnu.org/bugzilla/>
2022-01-04 5:29 ` egallager at gcc dot gnu.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=20080225181016.31735.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: link
Be 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).