From: Zopolis0 <creatorsmithmdt@gmail.com>
To: gcc-help <gcc-help@gcc.gnu.org>
Subject: Scope of 'new' TYPE_FIELDS and old TYPE_METHODS?
Date: Mon, 31 Oct 2022 21:36:11 +1100 [thread overview]
Message-ID: <CAEYL+X-Lvop6FaHR3t1SCn3RtXTUecHTFSXiUnZck7Dvq8b4_A@mail.gmail.com> (raw)
[-- 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?
reply other threads:[~2022-10-31 10:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAEYL+X-Lvop6FaHR3t1SCn3RtXTUecHTFSXiUnZck7Dvq8b4_A@mail.gmail.com \
--to=creatorsmithmdt@gmail.com \
--cc=gcc-help@gcc.gnu.org \
/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).