From: Paolo Carlini <paolo.carlini@oracle.com>
To: Chris Fairles <chris.fairles@gmail.com>
Cc: Gcc Patch List <gcc-patches@gcc.gnu.org>,
libstdc++ <libstdc++@gcc.gnu.org>
Subject: Re: [v3] c++0x <system_error> CD updates
Date: Tue, 14 Oct 2008 15:37:00 -0000 [thread overview]
Message-ID: <48F49CBA.9030004@oracle.com> (raw)
In-Reply-To: <fac6bb500810140609v526adfc5h4510da830910bd15@mail.gmail.com>
Chris Fairles wrote:
> FAIL: ext/mt_allocator/deallocate_local_thread-5.cc execution test
> FAIL: ext/mt_allocator/deallocate_local_thread-7.cc execution test
>
I don't think these are directly related to your work. These tests are
weak and fail for some targets already (I think there are issues with
the stack size).
> Besides those, feel free to comment/review. I'll post an updated patch
> once I figure out those segfaults.
>
Ok...
Paolo.
next prev parent reply other threads:[~2008-10-14 13:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-14 15:09 Chris Fairles
2008-10-14 15:37 ` Paolo Carlini [this message]
2008-10-15 16:08 ` Chris Fairles
2008-10-15 16:40 ` Paolo Carlini
2008-10-15 16:49 ` Chris Fairles
2008-10-15 16:51 ` Paolo Carlini
2008-10-22 14:23 ` Chris Fairles
2008-10-22 17:39 ` Paolo Carlini
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=48F49CBA.9030004@oracle.com \
--to=paolo.carlini@oracle.com \
--cc=chris.fairles@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@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).