From: Diego Novillo <dnovillo@google.com>
To: Richard Biener <richard.guenther@gmail.com>
Cc: Lawrence Crowl <crowl@google.com>,
nathan@codesourcery.com,
gcc-patches List <gcc-patches@gcc.gnu.org>
Subject: Re: [cxx-conversion] Add Record Builder Class
Date: Thu, 14 Feb 2013 11:56:00 -0000 [thread overview]
Message-ID: <CAD_=9DTAYk8VkUBt24D+CBQFiJ9GGEyP7M1op1ScM8zgmm17qw@mail.gmail.com> (raw)
In-Reply-To: <CAFiYyc2M5eSxfqyY_UueRw2=zm4CD=GqBLK+-GxOpi=MZsN19g@mail.gmail.com>
On Thu, Feb 14, 2013 at 4:26 AM, Richard Biener
<richard.guenther@gmail.com> wrote:
> Note that tag_name does not allow the way C++ uses this (it can be
> a TYPE_DECL).
>
> Overall I'm not sure this is a good abstraction unless you manage to
> make the frontends use it.
I think that is a mistake. This is a pure gimple facility. The fact
that it now looks somewhat similar to what front ends do is a
consequence of the state of the gimple type system.
We very specifically do not want to cater to front ends here. Why do
you think that should be a feature of this interface?
Diego.
next prev parent reply other threads:[~2013-02-14 11:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130209065835.F0DCF12084A@jade.mtv.corp.google.com>
2013-02-12 19:47 ` Lawrence Crowl
2013-02-13 19:42 ` Diego Novillo
2013-02-13 20:02 ` Lawrence Crowl
2013-02-13 20:08 ` Diego Novillo
2013-02-13 22:06 ` Lawrence Crowl
2013-02-14 9:26 ` Richard Biener
2013-02-14 11:56 ` Diego Novillo [this message]
2013-02-14 12:53 ` Richard Biener
2013-02-14 13:01 ` Diego Novillo
2013-02-14 13:07 ` Richard Biener
2013-02-14 13:41 ` Diego Novillo
2013-02-14 19:44 ` Lawrence Crowl
2013-02-15 9:04 ` Richard Biener
2013-02-15 14:21 ` Gabriel Dos Reis
2013-02-18 9:02 ` Nathan Sidwell
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='CAD_=9DTAYk8VkUBt24D+CBQFiJ9GGEyP7M1op1ScM8zgmm17qw@mail.gmail.com' \
--to=dnovillo@google.com \
--cc=crowl@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=nathan@codesourcery.com \
--cc=richard.guenther@gmail.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).