From: "J. Neuschäfer" <j.neuschaefer@gmx.net>
To: musl@lists.openwall.com
Cc: "J. Neuschäfer" <j.neuschaefer@gmx.net>
Subject: [musl] [PATCH MCM 0/3] musl-cross-make: add newer GCC versions
Date: Wed, 02 Oct 2024 17:40:03 +0200 [thread overview]
Message-ID: <20241002-gcc-bump-v1-0-8f910fd54b1c@gmx.net> (raw)
This patchset adds newer GCC versions to MCM. Patches are copied from
GCC 11 and only very lightly modifed (which can be verified by diffing
the patch directories).
I haven't tested the resulting toolchains, so there might be some bugs
lurking.
Signed-off-by: J. Neuschäfer <j.neuschaefer@gmx.net>
---
J. Neuschäfer (3):
add gcc 12.4 hash and patches
add gcc 13.3 hash and patches
add gcc 14.2 hash and patches
hashes/gcc-12.4.0.tar.xz.sha1 | 1 +
hashes/gcc-13.3.0.tar.xz.sha1 | 1 +
hashes/gcc-14.2.0.tar.xz.sha1 | 1 +
patches/gcc-12.4.0/0001-ssp_nonshared.diff | 14 +
patches/gcc-12.4.0/0002-posix_memalign.diff | 30 ++
patches/gcc-12.4.0/0003-j2.diff | 346 +++++++++++++++++++++
patches/gcc-12.4.0/0004-static-pie.diff | 92 ++++++
patches/gcc-12.4.0/0005-m68k-sqrt.diff | 20 ++
patches/gcc-12.4.0/0006-cow-libstdc++v3.diff | 8 +
patches/gcc-12.4.0/0007-fdpic-unwind.diff | 11 +
.../gcc-12.4.0/0008-fdpic-crtstuff-pr114158.diff | 38 +++
patches/gcc-12.4.0/0009-sh-fdpic-pr114641.diff | 12 +
patches/gcc-13.3.0/0001-ssp_nonshared.diff | 14 +
patches/gcc-13.3.0/0002-posix_memalign.diff | 30 ++
patches/gcc-13.3.0/0003-j2.diff | 346 +++++++++++++++++++++
patches/gcc-13.3.0/0004-static-pie.diff | 92 ++++++
patches/gcc-13.3.0/0005-m68k-sqrt.diff | 20 ++
patches/gcc-13.3.0/0006-cow-libstdc++v3.diff | 8 +
patches/gcc-13.3.0/0007-fdpic-unwind.diff | 11 +
.../gcc-13.3.0/0008-fdpic-crtstuff-pr114158.diff | 38 +++
patches/gcc-13.3.0/0009-sh-fdpic-pr114641.diff | 12 +
patches/gcc-14.2.0/0001-ssp_nonshared.diff | 14 +
patches/gcc-14.2.0/0002-posix_memalign.diff | 30 ++
patches/gcc-14.2.0/0003-j2.diff | 346 +++++++++++++++++++++
patches/gcc-14.2.0/0004-static-pie.diff | 92 ++++++
patches/gcc-14.2.0/0005-m68k-sqrt.diff | 20 ++
patches/gcc-14.2.0/0006-cow-libstdc++v3.diff | 8 +
patches/gcc-14.2.0/0007-fdpic-unwind.diff | 11 +
.../gcc-14.2.0/0008-fdpic-crtstuff-pr114158.diff | 38 +++
patches/gcc-14.2.0/0009-sh-fdpic-pr114641.diff | 12 +
30 files changed, 1716 insertions(+)
---
base-commit: fd6be58297ee21fcba89216ccd0d4aca1e3f1c5c
change-id: 20241002-gcc-bump-1d99a65a2422
Best regards,
--
J. Neuschäfer <j.neuschaefer@gmx.net>
next reply other threads:[~2024-10-02 15:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-02 15:40 J. Neuschäfer [this message]
2024-10-02 15:40 ` [musl] [PATCH MCM 1/3] add gcc 12.4 hash and patches J. Neuschäfer
2024-10-02 15:40 ` [musl] [PATCH MCM 2/3] add gcc 13.3 " J. Neuschäfer
2024-10-02 15:40 ` [musl] [PATCH MCM 3/3] add gcc 14.2 " J. Neuschäfer
2024-10-22 21:52 ` [musl] [PATCH MCM 0/3] musl-cross-make: add newer GCC versions Rich Felker
2024-10-23 12:29 ` J. Neuschäfer
2024-10-24 13:11 ` Rich Felker
2024-10-24 13:36 ` Rich Felker
2024-10-25 11:39 ` J. Neuschäfer
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=20241002-gcc-bump-v1-0-8f910fd54b1c@gmx.net \
--to=j.neuschaefer@gmx.net \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).