From: Paolo Carlini <paolo.carlini@oracle.com>
To: jyasskin@google.com
Cc: reply@codereview.appspotmail.com, gcc-patches@gcc.gnu.org,
Jason Merrill <jason@redhat.com>
Subject: Re: [patch] Fix two C++ errors in libstdc++. (issue4341041)
Date: Thu, 31 Mar 2011 19:49:00 -0000 [thread overview]
Message-ID: <4D94D8FE.30301@oracle.com> (raw)
In-Reply-To: <20110331190036.DABFE1695C9@enki.mtv.corp.google.com>
Hi,
> I think this is a candidate to backport to libstdc++-4.6.1.
>
> exception_ptr.h needs the forward declaration because it's
> included from<typeinfo> before<typeinfo> defines std::type_info.
before going ahead with the patch - I'm not at all sure it's enough, for
<exception> itself for example - I think we should understand why this
is accepted, note no headers:
namespace std
{
struct test
{
const type_info* fun();
};
}
Jason?
Paolo.
PS: remember to always post libstdc++ patches to the libstdc++ mailing
list too
next prev parent reply other threads:[~2011-03-31 19:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-31 19:06 Jeffrey Yasskin
2011-03-31 19:49 ` Paolo Carlini [this message]
2011-03-31 20:02 ` Paolo Carlini
2011-03-31 21:34 ` Jeffrey Yasskin
2011-03-31 22:10 ` Paolo Carlini
2011-03-31 21:26 ` Jason Merrill
2011-03-31 21:28 ` Paolo Carlini
2011-03-31 21:39 ` Jason Merrill
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=4D94D8FE.30301@oracle.com \
--to=paolo.carlini@oracle.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.com \
--cc=jyasskin@google.com \
--cc=reply@codereview.appspotmail.com \
/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).