From: Nathan Sidwell <nathan@acm.org>
To: GCC Patches <gcc-patches@gcc.gnu.org>
Cc: Jason Merrill <jason@redhat.com>,
Richard Guenther <richard.guenther@gmail.com>,
Jim Wilson <wilson@tuliptree.org>, Jan Hubicka <hubicka@ucw.cz>
Subject: [PATCH] Kill TYPE_METHODS 0/9
Date: Fri, 14 Jul 2017 16:44:00 -0000 [thread overview]
Message-ID: <8377f2cd-577c-60b2-63ac-f2619ebe63aa@acm.org> (raw)
This is a series of patches that remove the TYPE_METHODS field used in records &
unions. Currently TYPE_METHODS hods a the member functions (be they static or
non-static), and TYPE_FIELDS holds everything else (be they FIELD_DECLS or
whatever). This distinction is unnecessary, and the patches move everything to
TYPE_FIELDS. (I do not mess with name lookup, which is handled differently).
I do not repurpose TYPE_METHODS, that's later.
While the changes are pretty mechanical, some are rather too large outside of
the C++ FE to comfortably apply the obvious rule.
1 method-debug.diff - dbxout & dwarf2out. Review please.
2 method-ipa.diff - lto-devirt. Review please.
3 method-rtl.diff - most odd occurrence. Comment please.
4 method-ada.diff - ada-spec generation. Obvious.
5 method-cp.diff - C++ FE changes, self reviewed
6 method-libcc1.diff - libcp1plugin. Obvious.
7 method-misc.diff - random tree.c. Obvious.
8 method-objc.diff - objc. Obvious
9 method-ectomy.diff - delete the macro. Obvious
nathan
--
Nathan Sidwell
next reply other threads:[~2017-07-14 16:44 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-14 16:44 Nathan Sidwell [this message]
2017-07-14 16:49 ` [PATCH] Kill TYPE_METHODS debug 1/9 Nathan Sidwell
2017-07-18 17:24 ` Jim Wilson
2017-07-20 11:31 ` Nathan Sidwell
2017-07-20 12:13 ` Nathan Sidwell
2017-07-20 21:00 ` Nathan Sidwell
2017-07-20 22:04 ` Jim Wilson
2017-07-21 0:29 ` Nathan Sidwell
2017-07-21 5:11 ` Richard Biener
2017-07-21 13:08 ` Deprecate DBX/stabs? Nathan Sidwell
2017-07-21 13:16 ` Richard Biener
2017-07-21 14:06 ` Nathan Sidwell
2017-07-21 19:10 ` Mike Stump
2017-07-21 19:44 ` Iain Sandoe
2017-07-21 19:54 ` Jim Wilson
2017-07-21 20:12 ` Iain Sandoe
2017-07-22 1:22 ` JonY
2017-07-24 22:18 ` [PATCH] Kill TYPE_METHODS debug 1/9 Jeff Law
2017-07-14 16:51 ` [PATCH] Kill TYPE_METHODS ipa 2/9 Nathan Sidwell
2017-07-14 17:18 ` Jan Hubicka
2017-07-14 16:54 ` [PATCH] Kill TYPE_METHODS rtl 3/9 Nathan Sidwell
2017-07-15 4:43 ` Jeff Law
2017-07-15 12:20 ` Nathan Sidwell
2017-07-14 16:55 ` [PATCH] Kill TYPE_METHODS ada-spec 4/9 Nathan Sidwell
2017-07-14 16:57 ` [PATCH] Kill TYPE_METHODS c++ 5/9 Nathan Sidwell
2017-07-14 16:59 ` [PATCH] Kill TYPE_METHODS libcc1 6/9 Nathan Sidwell
2017-07-14 17:01 ` [PATCH] Kill TYPE_METHODS misc 7/9 Nathan Sidwell
2017-07-14 17:02 ` [PATCH] Kill TYPE_METHODS objc 8/9 Nathan Sidwell
2017-07-14 17:03 ` [PATCH] Kill TYPE_METHODS 9/9 Nathan Sidwell
2017-07-24 9:25 ` [PATCH] Kill TYPE_METHODS 0/9 Jakub Jelinek
2017-07-24 11:59 ` Nathan Sidwell
2017-07-25 16:06 ` Jim Wilson
2017-07-25 16:07 ` Jim Wilson
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=8377f2cd-577c-60b2-63ac-f2619ebe63aa@acm.org \
--to=nathan@acm.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=jason@redhat.com \
--cc=richard.guenther@gmail.com \
--cc=wilson@tuliptree.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).