From: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: Bump cross-arm-none-eabi gcc and binutils to match non-cross packages
Date: Thu, 26 Jan 2023 02:59:09 +0100 [thread overview]
Message-ID: <20230126015909.LmwGyGj0S4QdHqJP-i-XUtsbDzPr0E6UHypd8jHqrnw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37580@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 623 bytes --]
There's a closed pull request on the void-packages repository
Bump cross-arm-none-eabi gcc and binutils to match non-cross packages
https://github.com/void-linux/void-packages/pull/37580
Description:
#### Testing the changes
- I tested the changes in this PR: YES
I tested this with my own personal armv7 projects. Notably, the version currently in packages has a bug with LTO that makes it discard ISR functions/symbols inappropriately, making LTO useless for some embedded use cases. This appears fixed in gcc 10.
#### Local build testing
- I built this PR locally for my native architecture, amd64/glibc
next prev parent reply other threads:[~2023-01-26 1:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 1:38 [PR PATCH] " via
2022-06-18 13:50 ` [PR PATCH] [Updated] " via
2022-09-17 2:14 ` github-actions
2022-10-01 2:16 ` [PR PATCH] [Closed]: " github-actions
2022-10-01 9:06 ` JamiKettunen
2022-10-01 9:06 ` JamiKettunen
2022-10-05 18:04 ` JamiKettunen
2022-10-05 18:10 ` via
2022-10-05 18:14 ` paper42
2022-10-05 18:30 ` JamiKettunen
2022-10-05 18:31 ` JamiKettunen
2022-10-05 18:31 ` JamiKettunen
2022-10-13 2:26 ` [PR REVIEW] " wryun
2023-01-11 2:30 ` github-actions
2023-01-26 1:59 ` github-actions [this message]
2023-10-26 15:36 ` riddicc
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=20230126015909.LmwGyGj0S4QdHqJP-i-XUtsbDzPr0E6UHypd8jHqrnw@z \
--to=ml@inbox.vuxu.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 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).