public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <richard.guenther@gmail.com>
To: "Martin Liška" <mliska@suse.cz>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>, DJ Delorie <dj@redhat.com>
Subject: Re: [PATCH] m32c-rtems: remove obsoleted port
Date: Tue, 30 Aug 2022 15:43:30 +0200	[thread overview]
Message-ID: <CAFiYyc2P4UJQP+xsU5tALX8HLF3iXsAJLFmuO1RPFvofqZuzdg@mail.gmail.com> (raw)
In-Reply-To: <397ad854-62f7-47a1-453e-30b45098d4d9@suse.cz>

On Thu, Aug 25, 2022 at 10:37 AM Martin Liška <mliska@suse.cz> wrote:
>
> Remove the port that has been marked obsolete in GCC 12 change notes.
>
> Ready to be installed?

OK.

> Thanks,
> Martin
>
> contrib/ChangeLog:
>
>         * config-list.mk: Remove the port.
>
> gcc/ChangeLog:
>
>         * config.gcc: Remove the port.
>         * config/m32c/rtems.h: Removed.
>
> libgcc/ChangeLog:
>
>         * config.host: Remove the port.
> ---
>  contrib/config-list.mk  |  2 +-
>  gcc/config.gcc          |  6 ------
>  gcc/config/m32c/rtems.h | 38 --------------------------------------
>  libgcc/config.host      |  2 +-
>  4 files changed, 2 insertions(+), 46 deletions(-)
>  delete mode 100644 gcc/config/m32c/rtems.h
>
> diff --git a/contrib/config-list.mk b/contrib/config-list.mk
> index c4db8dc849a..015f3a83bc6 100644
> --- a/contrib/config-list.mk
> +++ b/contrib/config-list.mk
> @@ -59,7 +59,7 @@ LIST = aarch64-elf aarch64-linux-gnu aarch64-rtems \
>    ia64-freebsd6 ia64-linux ia64-hpux ia64-hp-vms iq2000-elf lm32-elf \
>    lm32-rtems lm32-uclinux \
>    loongarch64-linux-gnuf64 loongarch64-linux-gnuf32 loongarch64-linux-gnusf \
> -  m32c-rtems m32c-elf m32r-elf m32rle-elf \
> +  m32c-elf m32r-elf m32rle-elf \
>    m68k-elf m68k-netbsdelf \
>    m68k-uclinux m68k-linux m68k-rtems \
>    mcore-elf microblaze-linux microblaze-elf \
> diff --git a/gcc/config.gcc b/gcc/config.gcc
> index 02f58970db0..8e8e1d0513f 100644
> --- a/gcc/config.gcc
> +++ b/gcc/config.gcc
> @@ -251,7 +251,6 @@ case ${target} in
>   cr16-*-*                              \
>   | hppa[12]*-*-hpux10*                 \
>   | hppa[12]*-*-hpux11*                 \
> - | m32c-*-rtems*                       \
>   )
>      if test "x$enable_obsolete" != xyes; then
>        echo "*** Configuration ${target} is obsolete." >&2
> @@ -3555,11 +3554,6 @@ am33_2.0-*-linux*)
>         gas=yes gnu_ld=yes
>         use_collect2=no
>         ;;
> -m32c-*-rtems*)
> -       tm_file="elfos.h ${tm_file} m32c/rtems.h rtems.h newlib-stdint.h"
> -       c_target_objs="m32c-pragma.o"
> -       cxx_target_objs="m32c-pragma.o"
> -       ;;
>  m32c-*-elf*)
>         tm_file="elfos.h newlib-stdint.h ${tm_file}"
>         c_target_objs="m32c-pragma.o"
> diff --git a/gcc/config/m32c/rtems.h b/gcc/config/m32c/rtems.h
> deleted file mode 100644
> index 553f77cfd4d..00000000000
> --- a/gcc/config/m32c/rtems.h
> +++ /dev/null
> @@ -1,38 +0,0 @@
> -/* Definitions for rtems targeting a M32C using ELF.
> -   Copyright (C) 2008-2022 Free Software Foundation, Inc.
> -   Contributed by Joel Sherrill (joel@OARcorp.com).
> -
> -   This file is part of GCC.
> -
> -   GCC is free software; you can redistribute it and/or modify it
> -   under the terms of the GNU General Public License as published
> -   by the Free Software Foundation; either version 3, or (at your
> -   option) any later version.
> -
> -   GCC is distributed in the hope that it will be useful, but WITHOUT
> -   ANY WARRANTY; without even the implied warranty of MERCHANTABILITY
> -   or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public
> -   License for more details.
> -
> -   Under Section 7 of GPL version 3, you are granted additional
> -   permissions described in the GCC Runtime Library Exception, version
> -   3.1, as published by the Free Software Foundation.
> -
> -   You should have received a copy of the GNU General Public License and
> -   a copy of the GCC Runtime Library Exception along with this program;
> -   see the files COPYING3 and COPYING.RUNTIME respectively.  If not, see
> -   <http://www.gnu.org/licenses/>.  */
> -
> -/* Target OS builtins.  */
> -#undef TARGET_OS_CPP_BUILTINS
> -#define TARGET_OS_CPP_BUILTINS()               \
> -  do                                           \
> -    {                                          \
> -       builtin_define ("__rtems__");           \
> -       builtin_define ("__USE_INIT_FINI__");   \
> -       builtin_assert ("system=rtems");        \
> -    }                                          \
> -  while (0)
> -
> -/* Use the default */
> -#undef LINK_GCC_C_SEQUENCE_SPEC
> diff --git a/libgcc/config.host b/libgcc/config.host
> index b2a0a8e1aa9..974de349653 100644
> --- a/libgcc/config.host
> +++ b/libgcc/config.host
> @@ -1516,7 +1516,7 @@ am33_2.0-*-linux*)
>         extra_parts="crtbegin.o crtend.o crtbeginS.o crtendS.o"
>         tmake_file="$tmake_file t-fdpbit"
>         ;;
> -m32c-*-elf*|m32c-*-rtems*)
> +m32c-*-elf*)
>         tmake_file="$tmake_file m32c/t-m32c"
>         ;;
>  nvptx-*)
> --
> 2.37.2
>

      parent reply	other threads:[~2022-08-30 13:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-25  8:36 Martin Liška
2022-08-25  8:36 ` Martin Liška
2022-08-30 13:43 ` Richard Biener [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=CAFiYyc2P4UJQP+xsU5tALX8HLF3iXsAJLFmuO1RPFvofqZuzdg@mail.gmail.com \
    --to=richard.guenther@gmail.com \
    --cc=dj@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=mliska@suse.cz \
    /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).