From: Chung-Lin Tang <cltang@baylibre.com>
To: Arnd Bergmann <arnd@arndb.de>,
"schuster.simon@siemens-energy.com"
<schuster.simon@siemens-energy.com>
Cc: "Dinh Nguyen" <dinguyen@kernel.org>,
"Thomas Weißschuh" <thomas.weissschuh@linutronix.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] nios2: remove libgcc for lshrdi3, ashldi3, ashrdi3, muldi3, and ucmpdi2
Date: Wed, 21 Oct 2026 18:35:35 +0800 [thread overview]
Message-ID: <5b408217-52d1-4a22-b15b-1f0a560906f0@baylibre.com> (raw)
In-Reply-To: <686f4ca2-0fb6-4a73-9cdb-0edcccafdd62@app.fastmail.com>
On 10/20/26 5:41 PM, Arnd Bergmann wrote:
>> On a more practical note, while technically feasible, I'm not sure
>> whether we can actually vendor/copy directly from libgcc; I think all
>> code there is GPLv3 with Runtime Exception. (I'm not a lawyer yadayada),
>> but I guess direct reuse in that way is problematic, given that the
>> kernel is GPLv2 only? So I guess we would need to do a reimplementation?
> Right, the easiest way would be if you can locate a downstream gcc
> (or clang) fork from Altera or Codesourcery before it was merged,
> if that still has GPLv2 or a more liberal license. Reimplementing
> the functions otherwise is of course annoying.
>
> Adding Chung-Lin Tang to Cc, they contributed the original files
> to gcc back in 2013 and may know a copyright holder that can
> provide a GPLv2 compatible copy.
You're in luck, found the old GCC patches still exist online:
https://github.com/openembedded/openembedded/commit/77c8a823d4490619a247b0d4c0897761003acf98
They appear to be GPLv2 branded, hope this is of use.
Chung-Lin
prev parent reply other threads:[~2026-10-21 10:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-19 16:50 Dinh Nguyen
2026-10-19 16:50 ` [PATCH 2/2] nios2: remove 64-bit division Dinh Nguyen
2026-10-19 21:14 ` Arnd Bergmann
2026-10-19 21:20 ` [PATCH 1/2] nios2: remove libgcc for lshrdi3, ashldi3, ashrdi3, muldi3, and ucmpdi2 Arnd Bergmann
2026-10-20 8:56 ` Simon Schuster
2026-10-20 9:41 ` Arnd Bergmann
2026-10-20 12:31 ` Simon Schuster
2026-10-20 12:55 ` Arnd Bergmann
2026-10-21 10:35 ` Chung-Lin Tang [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=5b408217-52d1-4a22-b15b-1f0a560906f0@baylibre.com \
--to=cltang@baylibre.com \
--cc=arnd@arndb.de \
--cc=dinguyen@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=schuster.simon@siemens-energy.com \
--cc=thomas.weissschuh@linutronix.de \
/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
all inboxes | Powered by JetHome®