From: Joel Sherrill <joel@rtems.org>
To: Joseph Myers <josmyers@redhat.com>
Cc: Sandra Loosemore <sloosemore@baylibre.com>,
gcc@gcc.gnu.org, binutils@sourceware.org,
gdb-patches@sourceware.org, libc-alpha@sourceware.org,
Chung-Lin Tang <cltang@baylibre.com>,
andrew@reenigne.org, Yao Qi <qiyaoltc@gmail.com>,
Dinh Nguyen <dinguyen@kernel.org>,
qemu-devel@nongnu.org, newlib@sourceware.org,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: Deprecation/removal of nios2 target support
Date: Thu, 18 Apr 2024 10:57:18 -0500 [thread overview]
Message-ID: <CAF9ehCVZddmGe0emH8H6ChjuUxia-NOpxa0dCA=5+2PAnvytZA@mail.gmail.com> (raw)
In-Reply-To: <b5d375ed-283-974a-febf-892760ff855@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 791 bytes --]
On Thu, Apr 18, 2024 at 10:46 AM Joseph Myers <josmyers@redhat.com> wrote:
> On Wed, 17 Apr 2024, Sandra Loosemore wrote:
>
> > Therefore I'd like to mark Nios II as obsolete in GCC 14 now, and remove
> > support from all toolchain components after the release is made. I'm
> not sure
> > there is an established process for obsoleting/removing support in other
> > components; besides binutils, GDB, and GLIBC, there's QEMU,
> newlib/libgloss,
> > and the Linux kernel. But, we need to get the ball rolling somewhere.
>
> CC:ing Arnd Bergmann regarding the obsolescence in the Linux kernel.
>
Just an FYI that the RTEMS Project plans to drop NIOS II support based
on what happens with the tooling.
--joel
>
> --
> Joseph S. Myers
> josmyers@redhat.com
>
>
next prev parent reply other threads:[~2024-04-18 15:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-18 3:27 Sandra Loosemore
2024-04-18 5:53 ` Thomas Huth
2024-04-18 12:49 ` Marek Vasut
2024-04-18 15:44 ` Joseph Myers
2024-04-18 15:57 ` Joel Sherrill [this message]
2024-04-18 16:06 ` Jeff Law
2024-04-18 17:00 ` Sandra Loosemore
2024-04-18 18:41 ` Arnd Bergmann
2024-04-19 3:50 ` Marek Vasut
2024-04-19 12:05 ` Dinh Nguyen
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='CAF9ehCVZddmGe0emH8H6ChjuUxia-NOpxa0dCA=5+2PAnvytZA@mail.gmail.com' \
--to=joel@rtems.org \
--cc=andrew@reenigne.org \
--cc=arnd@arndb.de \
--cc=binutils@sourceware.org \
--cc=cltang@baylibre.com \
--cc=dinguyen@kernel.org \
--cc=gcc@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=josmyers@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=newlib@sourceware.org \
--cc=qemu-devel@nongnu.org \
--cc=qiyaoltc@gmail.com \
--cc=sloosemore@baylibre.com \
/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).