public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: Dinh Nguyen <dinguyen@kernel.org>
To: Arnd Bergmann <arnd@arndb.de>, Joseph Myers <josmyers@redhat.com>,
	Sandra Loosemore <sloosemore@baylibre.com>
Cc: gcc@gcc.gnu.org, binutils@sourceware.org,
	gdb-patches@sourceware.org, Xi Ruoyao <libc-alpha@sourceware.org>,
	Chung-Lin Tang <cltang@baylibre.com>,
	andrew@reenigne.org, Yao Qi <qiyaoltc@gmail.com>,
	qemu-devel@nongnu.org, newlib@sourceware.org,
	Andreas Oetken <andreas.oetken@siemens.com>,
	Bernd Weiberg <bernd.weiberg@siemens.com>,
	Marek Vasut <marex@denx.de>
Subject: Re: Deprecation/removal of nios2 target support
Date: Fri, 19 Apr 2024 07:05:04 -0500	[thread overview]
Message-ID: <975c8ed9-e0b0-4b5e-8a4c-0970c98fa3e6@kernel.org> (raw)
In-Reply-To: <320677a6-1c3a-477c-95fc-b74cb5a4c5c6@app.fastmail.com>



On 4/18/24 13:41, Arnd Bergmann wrote:
> On Thu, Apr 18, 2024, at 17:44, Joseph Myers 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.
> 
> We have not yet marked nios2 as deprecated in the kernel, but that
> is mostly because the implementation does not get in the way too
> much and Dinh Nguyen is still around as a maintainer and merging
> bugfixes.
> 
> Almost all nios2 kernel changes I see in the past decade have been
> done blindly without testing on hardware, either for treewide
> changes, or by code inspection. The only notable exceptions I could
> find are from Andreas Oetken and Bernd Weiberg at Siemens and
> from Marek Vasut (all added to Cc in case they have something to add).
> 
> We should probably remove nios2 from the kernel in the near future,
> but even if we decide not to, I think deprecating it from gcc is the
> right idea: If there are a few remaining users that still plan
> to update their kernels, gcc-14 will still be able to build new
> kernels for several years.
> 

I'm planning to do this soon.

Dinh

      parent reply	other threads:[~2024-04-19 12:05 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
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 [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=975c8ed9-e0b0-4b5e-8a4c-0970c98fa3e6@kernel.org \
    --to=dinguyen@kernel.org \
    --cc=andreas.oetken@siemens.com \
    --cc=andrew@reenigne.org \
    --cc=arnd@arndb.de \
    --cc=bernd.weiberg@siemens.com \
    --cc=binutils@sourceware.org \
    --cc=cltang@baylibre.com \
    --cc=gcc@gcc.gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=josmyers@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=marex@denx.de \
    --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).