From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: [ptxdist] [ANNOUNCE] OSELAS.Toolchain() 2022.10.1 released
Date: Fri, 2 Jun 2023 08:53:17 +0200 [thread overview]
Message-ID: <ZHmR3e6uW8ZbgbmU@pengutronix.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1601 bytes --]
Hi,
I'm happy to announce that I've just released OSELAS.Toolchain-2022.10.1.
This is a bugfix only release. There are no major update. The relevant
changes are:
- In previous releases, libstdc++ was not built correctly and
optimizations where disabled. This is fixed now. Updating to this new
version can result in significant performance improvements in certain
use-cases.
- gcc was updated to the 12-20230519 snapshot release. Note, that the
reported version is now 12.3.1 so the platformconfig in PTXdist BSPs
must be updated accordingly.
- glibc was updated to 2.36-100-g93bd77104cdd in the 2.36 stable branch.
- All patches from the binutils 2.39 stable branch that seemed relevant
have been cherry-picked.
- llvm, clang and lld where update to the 15.0.7 stable release.
Download the release here:
https://public.pengutronix.de/oselas/toolchain/
Debian / Ubuntu Packages will be available at
http://debian.pengutronix.de/
For the binary packages, the plan is the same as for the v2022.10.0
release: I plan is to build packages for Debian bookworm/sid, bullseye,
buster and Ubuntu 18.04, 20.04, 22.04. I may build toolchains for Debian
stretch and Ubuntu 16.04 but that depends on how easy that is.
Enjoy,
Michael Olbrich
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
reply other threads:[~2023-06-02 6:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=ZHmR3e6uW8ZbgbmU@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.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