public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Manuel López-Ibáñez" <lopezibanez@gmail.com>
To: Ian Lance Taylor <iant@google.com>
Cc: basile@starynkevitch.net, gcc@gcc.gnu.org
Subject: Re: what are exactly GCC core types?
Date: Tue, 22 Jun 2010 07:19:00 -0000	[thread overview]
Message-ID: <AANLkTikb9AvIuoEcPikWKHGQf8gczHhL8ox8v4rW_Wlm@mail.gmail.com> (raw)
In-Reply-To: <mcrfx0foa2z.fsf@dhcp-172-17-9-151.mtv.corp.google.com>

On 22 June 2010 08:28, Ian Lance Taylor <iant@google.com> wrote:
> Basile Starynkevitch <basile@starynkevitch.net> writes:
>
>> What are exactly GCC code types, defined in gcc/coretypes.h?
>
> They are types for which there was no obvious place to put them.
>
>> Of course, they are very important types used in GCC. And there are
>> probably wired in gengtype (but maybe not all of them; I didn't check
>> for all; certainly gengtype handle tree & gimple specially in some
>> way.).
>
> gengtype only handles a few types specially.  There is no particular
> connection between types recognized by gengtype and coretypes.h.
> E.g., gengtype handles VEC specially, but it is not in coretypes.h.
>
>> However, I don't understand why gimple_seq_node is a core type. It seems
>> rarely used (outside of gimple*.[ch] files), and I would imagine it
>> could be kept in gimple.h.
>
> I agree.  I expect it's there just because gimple_seq is there.
>

Basile, if you can move it to gimple.h and bootstrap + regression
test, then I am pretty sure such a patch would be accepted. If moving
it breaks something, then probably there is a reason for it to be
there and if it is not easy to fix it, at least, you can add a
comment.

Manuel.

  reply	other threads:[~2010-06-22  7:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-22  6:58 Basile Starynkevitch
2010-06-22  7:05 ` Ian Lance Taylor
2010-06-22  7:19   ` Manuel López-Ibáñez [this message]
2010-06-22 14:52 ` Joseph S. Myers

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=AANLkTikb9AvIuoEcPikWKHGQf8gczHhL8ox8v4rW_Wlm@mail.gmail.com \
    --to=lopezibanez@gmail.com \
    --cc=basile@starynkevitch.net \
    --cc=gcc@gcc.gnu.org \
    --cc=iant@google.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).