From: David Krauss <potswa@gmail.com>
To: gcc-patches@gcc.gnu.org
Subject: Re: Movable initializer lists (C++ N4166)
Date: Wed, 06 May 2015 10:18:00 -0000 [thread overview]
Message-ID: <FBC9DDBF-B9F5-4F1D-8C7F-7A01FFDAF20B@gmail.com> (raw)
In-Reply-To: <7F4F7451-0753-431B-9C7D-98BD100BAF85@gmail.com>
> On 2015–05–04, at 12:00 AM, David Krauss <potswa@gmail.com> wrote:
>
> Besides that, are some machines overloaded? If I need to use POWER, will there be a learning curve or brittleness as on Darwin? To avoid trial and error whilst wading into the process, I’m just asking for some personal confirmation of suitability for my particular needs: same-day turnaround for clean rebuilds + testsuite validation. Too many days of my life have gone into setting up GCC builds (and then setting up again elsewhere when a problem comes up).
Just to follow up: The POWER8 machine, gcc112, is a beast. Maybe it’s my time zone, but I’m getting all 152 threads to myself. No significant “background” load or other users typically hanging around. POWER does seem to have a few extra testcase failures, but no particular quirks for the uninitiated.
Glad I signed up.
prev parent reply other threads:[~2015-05-06 10:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-03 14:48 David Krauss
2015-05-03 15:27 ` Marc Glisse
2015-05-03 16:00 ` David Krauss
2015-05-06 10:18 ` David Krauss [this message]
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=FBC9DDBF-B9F5-4F1D-8C7F-7A01FFDAF20B@gmail.com \
--to=potswa@gmail.com \
--cc=gcc-patches@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).