From: "Ionen Wolkens" <ionen@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-util/mingw64-toolchain/
Date: Wed, 22 May 2024 03:32:23 +0000 (UTC) [thread overview]
Message-ID: <1716348657.3cd1ffe8b0e1fd84a98501ccca0a8ccefd40c307.ionen@gentoo> (raw)
commit: 3cd1ffe8b0e1fd84a98501ccca0a8ccefd40c307
Author: Ionen Wolkens <ionen <AT> gentoo <DOT> org>
AuthorDate: Wed May 22 02:11:07 2024 +0000
Commit: Ionen Wolkens <ionen <AT> gentoo <DOT> org>
CommitDate: Wed May 22 03:30:57 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=3cd1ffe8
Revert "dev-util/mingw64-toolchain: add workaround for gcc14 ICE w/ mingw"
This reverts commit b6ca4f9dc1b3e4f9e947e547f9cab2730502de52.
A fix was found, so will patch gcc instead.
Bug: https://bugs.gentoo.org/932319
Signed-off-by: Ionen Wolkens <ionen <AT> gentoo.org>
dev-util/mingw64-toolchain/mingw64-toolchain-11.0.1.ebuild | 3 ---
1 file changed, 3 deletions(-)
diff --git a/dev-util/mingw64-toolchain/mingw64-toolchain-11.0.1.ebuild b/dev-util/mingw64-toolchain/mingw64-toolchain-11.0.1.ebuild
index adae7ba4e0d5..8f3671e17f67 100644
--- a/dev-util/mingw64-toolchain/mingw64-toolchain-11.0.1.ebuild
+++ b/dev-util/mingw64-toolchain/mingw64-toolchain-11.0.1.ebuild
@@ -237,9 +237,6 @@ src_compile() {
# znver4: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110273
append-flags -mno-avx
- # gcc14 -fno-omit-frame-pointer ICE workaround (bug #932319)
- append-flags -fomit-frame-pointer
-
strip-unsupported-flags
mwt-build "${@:2}"
)
next reply other threads:[~2024-05-22 3:32 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-22 3:32 Ionen Wolkens [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-03 12:31 [gentoo-commits] repo/gentoo:master commit in: dev-util/mingw64-toolchain/ Ionen Wolkens
2024-07-02 21:09 Jakov Smolić
2024-07-02 21:09 Jakov Smolić
2024-06-06 13:20 Ionen Wolkens
2024-06-02 3:54 Ionen Wolkens
2024-05-30 6:39 Ionen Wolkens
2024-05-21 3:01 Ionen Wolkens
2024-05-10 10:12 Ionen Wolkens
2024-05-10 3:03 Ionen Wolkens
2024-05-07 17:49 Ionen Wolkens
2024-05-07 14:28 Ionen Wolkens
2024-05-07 14:28 Ionen Wolkens
2024-03-24 18:39 Ionen Wolkens
2024-02-22 14:27 Ionen Wolkens
2024-01-16 17:52 Ionen Wolkens
2023-12-22 17:38 Ionen Wolkens
2023-08-27 17:18 Sam James
2023-08-27 1:28 Sam James
2023-08-04 3:25 Ionen Wolkens
2023-08-04 3:25 Ionen Wolkens
2023-07-30 16:52 Ionen Wolkens
2023-07-28 5:16 Ionen Wolkens
2023-07-03 20:55 Ionen Wolkens
2023-06-26 10:12 Ionen Wolkens
2023-05-29 17:49 Arthur Zamarin
2023-05-29 15:06 Sam James
2023-05-19 1:41 Ionen Wolkens
2023-05-11 17:01 Ionen Wolkens
2023-04-29 9:43 Ionen Wolkens
2023-04-26 8:37 Ionen Wolkens
2023-04-26 8:37 Ionen Wolkens
2023-02-01 21:04 Ionen Wolkens
2023-01-15 7:00 Ionen Wolkens
2022-11-12 11:33 Ionen Wolkens
2022-10-31 0:54 Ionen Wolkens
2022-10-23 7:20 Ionen Wolkens
2022-09-16 16:17 Ionen Wolkens
2022-09-16 7:54 Ionen Wolkens
2022-09-16 7:47 Ionen Wolkens
2022-09-14 23:11 Ionen Wolkens
2022-09-14 21:12 Ionen Wolkens
2022-09-14 19:39 Ionen Wolkens
2022-08-29 6:55 Ionen Wolkens
2022-08-29 6:55 Ionen Wolkens
2022-08-20 13:58 Ionen Wolkens
2022-08-20 13:45 Ionen Wolkens
2022-08-20 13:45 Ionen Wolkens
2022-07-16 17:03 Ionen Wolkens
2022-06-28 5:56 Ionen Wolkens
2022-05-28 19:26 Ionen Wolkens
2022-05-17 6:53 Jakov Smolić
2022-05-17 6:53 Jakov Smolić
2022-05-13 6:53 Ionen Wolkens
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=1716348657.3cd1ffe8b0e1fd84a98501ccca0a8ccefd40c307.ionen@gentoo \
--to=ionen@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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