From: Ben Hutchings <ben-/+tVBieCtBitmTQ+vhA3Yw@public.gmane.org>
To: klibc mailing list <klibc-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>
Cc: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [ANNOUNCE] klibc 2.0.10
Date: Thu, 30 Dec 2021 16:29:43 +0100 [thread overview]
Message-ID: <f62bebd13c95321c23cf982dd03c54d6bb57fb35.camel@decadent.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 1785 bytes --]
I have released version 2.0.10. This is available in the git
repository at:
https://git.kernel.org/pub/scm/libs/klibc/klibc.git
and as a tarball at:
https://mirrors.kernel.org/pub/linux/libs/klibc/2.0/
New features:
- s390x and sparc64 ports can now be compiled using Clang
- arm port can now be linked using LLD
Bug fixes:
- sig{set,long}jmp now honour the savesigs flag
- s390x: {set,long}jmp now save and restore correct FP registers
- utimes used to set incorrect mtime on architectures which do not
have a utimes systtem call
- Fixed build failure in dash when using Clang 13
- arm64,x86_64: Fixed address collision when using LLD 13
- Headers consistently use definitions from <sys/types.h> instead of
<linux/types.h>
A git shortlog of changes since version 2.0.9 follows.
Ben.
Ben Hutchings (8):
[klibc] 2.0.9 released, next version is 2.0.10
[klibc] Kbuild: Fix include path for Clang builds
[klibc] Use bounded array parameter types consistently
[klibc] include: Always include <sys/types.h> instead of <linux/types.h>
[klibc] arm: Remove redundant/unsupported linker option --thumb-entry
[klibc] s390: mmap: Change inline assembly to work with Clang
[klibc] sparc64: Remove redundant/unsupported compiler option -mptr64
[klibc] arm64,x86_64: Fix address collision when using LLD
Benjamin Gwin (1):
[klibc] Fix implementation of utimes
mirabilos (2):
sig{set,long}jmp: do not ignore sigsetjmp's second argument
{set,long}jmp [s390x]: save/restore the correct registers
--
Ben Hutchings
Experience is directly proportional to the value of equipment destroyed
- Carolyn Scheppner
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2021-12-30 15:29 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=f62bebd13c95321c23cf982dd03c54d6bb57fb35.camel@decadent.org.uk \
--to=ben-/+tvbiectbitmtq+vha3yw@public.gmane.org \
--cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=klibc-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.