From: Bill Schmidt <wschmidt@linux.ibm.com>
To: gcc-patches@gcc.gnu.org
Cc: dje.gcc@gmail.com, segher@kernel.crashing.org
Subject: Re: [PATCH v2 0/6] Remove "old" built-in function infrastructure
Date: Tue, 14 Dec 2021 11:32:16 -0600 [thread overview]
Message-ID: <1dee7c82-fd0f-481a-3cff-1b7fd1cec43d@linux.ibm.com> (raw)
In-Reply-To: <cover.1638820430.git.wschmidt@linux.ibm.com>
Hi! I'd like to ping patches 2 through 6 of this series. Much obliged!
Thanks,
Bill
On 12/6/21 2:49 PM, Bill Schmidt via Gcc-patches wrote:
> Hi!
>
> Now that the new built-in function support is all upstream and enabled, it
> seems safe and prudent to remove the old code to avoid confusion. I broke this
> up to the extent possible, but a couple of patches are still pretty large.
>
> David Edelsohn found that I had broken some C++ library functions for AIX, and
> his fix for that required me to re-spin the patches. I also generated the diff
> with a more efficient algorithm to reduce the patch size. Otherwise this
> series is identical to V1.
>
> Thanks!
> Bill
>
> Bill Schmidt (6):
> rs6000: Remove new_builtins_are_live and dead code it was guarding
> rs6000: Remove altivec_overloaded_builtins array and initialization
> rs6000: Rename rs6000-builtin-new.def to rs6000-builtins.def
> rs6000: Remove rs6000-builtin.def and associated data and functions
> rs6000: Rename functions with "new" in their names
> rs6000: Rename arrays to remove temporary _x suffix
>
> gcc/config/rs6000/darwin.h | 8 +-
> gcc/config/rs6000/rs6000-builtin.def | 3350 -----
> ...00-builtin-new.def => rs6000-builtins.def} | 0
> gcc/config/rs6000/rs6000-c.c | 1266 +-
> gcc/config/rs6000/rs6000-call.c | 11964 +---------------
> gcc/config/rs6000/rs6000-gen-builtins.c | 115 +-
> gcc/config/rs6000/rs6000-internal.h | 2 +-
> gcc/config/rs6000/rs6000-protos.h | 3 -
> gcc/config/rs6000/rs6000.c | 334 +-
> gcc/config/rs6000/rs6000.h | 58 -
> gcc/config/rs6000/t-rs6000 | 7 +-
> 11 files changed, 224 insertions(+), 16883 deletions(-)
> delete mode 100644 gcc/config/rs6000/rs6000-builtin.def
> rename gcc/config/rs6000/{rs6000-builtin-new.def => rs6000-builtins.def} (100%)
>
prev parent reply other threads:[~2021-12-14 17:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-06 20:49 Bill Schmidt
2021-12-06 20:49 ` [PATCH 1/6] rs6000: Remove new_builtins_are_live and dead code it was guarding Bill Schmidt
2021-12-07 1:09 ` Segher Boessenkool
2021-12-06 20:49 ` [PATCH 2/6] rs6000: Remove altivec_overloaded_builtins array and initialization Bill Schmidt
2021-12-14 17:57 ` [PATCH v2 " Bill Schmidt
2021-12-14 18:04 ` [PATCH " David Edelsohn
2021-12-06 20:49 ` [PATCH 3/6] rs6000: Rename rs6000-builtin-new.def to rs6000-builtins.def Bill Schmidt
2021-12-14 18:00 ` [PATCH v2 " Bill Schmidt
2021-12-14 18:05 ` [PATCH " David Edelsohn
2021-12-06 20:49 ` [PATCH 4/6] rs6000: Remove rs6000-builtin.def and associated data and functions Bill Schmidt
2021-12-14 18:00 ` [PATCH v2 " Bill Schmidt
2021-12-14 18:08 ` [PATCH " David Edelsohn
2021-12-06 20:49 ` [PATCH 5/6] rs6000: Rename functions with "new" in their names Bill Schmidt
2021-12-14 18:01 ` [PATCH v2 /6] " Bill Schmidt
2021-12-14 18:08 ` [PATCH 5/6] " David Edelsohn
2021-12-06 20:49 ` [PATCH 6/6] rs6000: Rename arrays to remove temporary _x suffix Bill Schmidt
2021-12-14 18:01 ` [PATCH v2 " Bill Schmidt
2021-12-14 18:10 ` [PATCH " David Edelsohn
2021-12-14 17:32 ` Bill Schmidt [this message]
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=1dee7c82-fd0f-481a-3cff-1b7fd1cec43d@linux.ibm.com \
--to=wschmidt@linux.ibm.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=segher@kernel.crashing.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).