From: Jeff Law <jeffreyalaw@gmail.com>
To: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] cr16: remove obsoleted port
Date: Thu, 25 Aug 2022 09:45:58 -0600 [thread overview]
Message-ID: <5c8c53af-1c0c-b9e4-92e6-b8a7c871aff8@gmail.com> (raw)
In-Reply-To: <3bebadac-9916-2283-9aae-e5142b14c7ef@suse.cz>
On 8/25/2022 2:38 AM, Martin Liška wrote:
> Remove the port that has been marked obsolete in GCC 12 change notes.
>
> Ready to be installed?
> Thanks,
> Martin
>
> ChangeLog:
>
> * config.sub: Remove cr16.
>
> contrib/ChangeLog:
>
> * config-list.mk: Remove cr16.
>
> gcc/ChangeLog:
>
> * config.gcc: Remove cr16 related stuff.
> * doc/extend.texi: Likewise.
> * doc/install.texi: Likewise.
> * doc/invoke.texi: Likewise.
> * doc/md.texi: Likewise.
> * function-tests.cc (test_expansion_to_rtl): Likewise.
> * common/config/cr16/cr16-common.cc: Removed.
> * config/cr16/constraints.md: Removed.
> * config/cr16/cr16-protos.h: Removed.
> * config/cr16/cr16.cc: Removed.
> * config/cr16/cr16.h: Removed.
> * config/cr16/cr16.md: Removed.
> * config/cr16/cr16.opt: Removed.
> * config/cr16/predicates.md: Removed.
> * config/cr16/t-cr16: Removed.
>
> libgcc/ChangeLog:
>
> * config.host: Remove cr16 related stuff.
> * config/cr16/crti.S: Removed.
> * config/cr16/crtlibid.S: Removed.
> * config/cr16/crtn.S: Removed.
> * config/cr16/divmodhi3.c: Removed.
> * config/cr16/lib1funcs.S: Removed.
> * config/cr16/t-cr16: Removed.
> * config/cr16/t-crtlibid: Removed.
> * config/cr16/unwind-cr16.c: Removed.
> * config/cr16/unwind-dw2.h: Removed.
LGTM. If any additional cr16 bits are found, feel free to remove them too.
jeff
next prev parent reply other threads:[~2022-08-25 15:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-25 8:38 Martin Liška
2022-08-25 8:38 ` Martin Liška
2022-08-25 12:48 ` Jan-Benedict Glaw
2022-08-25 12:50 ` Martin Liška
2022-08-25 12:58 ` Jan-Benedict Glaw
2022-08-25 15:45 ` Jeff Law [this message]
2022-08-25 16:54 ` Joseph Myers
2022-08-25 16:54 ` Joseph Myers
2022-08-26 6:19 ` Martin Liška
2022-08-25 17:06 ` Andrew Pinski
2022-08-26 6:20 ` Martin Liška
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=5c8c53af-1c0c-b9e4-92e6-b8a7c871aff8@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@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).