public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
* Scope of 'new' TYPE_FIELDS and old TYPE_METHODS?
@ 2022-10-31 10:36 Zopolis0
  0 siblings, 0 replies; only message in thread
From: Zopolis0 @ 2022-10-31 10:36 UTC (permalink / raw)
  To: gcc-help

[-- Attachment #1: Type: text/plain, Size: 535 bytes --]

In 5aaa8fb40681ee66282d73dab8c8eccbf5ee0518, TYPE_METHODS was removed and
TYPE_FIELDS replaced it.

In doing so, the scope of TYPE_FIELDS expanded, as it now output new tree
types.

The java frontend made heavy use of TYPE_METHODS and TYPE_FIELDS, and so I
am encountering numerous issues in my attempt to convert the TYPE_METHODS
calls into TYPE_FIELDS calls.

So, what did 5aaa8fb change? What does a TYPE_FIELD call output compared to
what it did before, and what subset of that is equivalent to what a
TYPE_METHOD call used to be?

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2022-10-31 10:36 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-10-31 10:36 Scope of 'new' TYPE_FIELDS and old TYPE_METHODS? Zopolis0

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).