From: Richard Henderson <rth@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Jason Merrill <jason@redhat.com>,
"Joseph S. Myers" <joseph@codesourcery.com>,
gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Use TYPE_NEXT_VARIANT instead of TREE_CHAIN as chain_next for types during GC (PR c++/46400)
Date: Mon, 27 Jun 2011 16:59:00 -0000 [thread overview]
Message-ID: <4E08B4BA.3080204@redhat.com> (raw)
In-Reply-To: <20110627164241.GC16443@tyan-ft48-01.lab.bos.redhat.com>
On 06/27/2011 09:42 AM, Jakub Jelinek wrote:
> 2011-06-27 Jakub Jelinek <jakub@redhat.com>
>
> * c-common.h (c_tree_chain_next): New static inline function.
>
> * c-decl.c (union lang_tree_node): Use it in chain_next expression.
>
> * cp-tree.h (union lang_tree_node): Use it in chain_next expression.
Ok. Thanks.
r~
prev parent reply other threads:[~2011-06-27 16:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-24 14:58 Jakub Jelinek
2011-06-24 19:49 ` Joseph S. Myers
2011-06-24 23:13 ` Jason Merrill
2011-06-24 23:15 ` Richard Henderson
2011-06-27 16:50 ` Jakub Jelinek
2011-06-27 16:59 ` Richard Henderson [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=4E08B4BA.3080204@redhat.com \
--to=rth@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=jason@redhat.com \
--cc=joseph@codesourcery.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).