From: "Mike Gilbert" <floppym@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/gcc-multilib-bootstrap:master commit in: /
Date: Sun, 17 Apr 2022 17:48:24 +0000 (UTC) [thread overview]
Message-ID: <1650215503.22181da2a393a2e3d47da511a49e958e649c15c0.floppym@gentoo> (raw)
commit: 22181da2a393a2e3d47da511a49e958e649c15c0
Author: Mike Gilbert <floppym <AT> gentoo <DOT> org>
AuthorDate: Sun Apr 17 17:11:43 2022 +0000
Commit: Mike Gilbert <floppym <AT> gentoo <DOT> org>
CommitDate: Sun Apr 17 17:11:43 2022 +0000
URL: https://gitweb.gentoo.org/proj/gcc-multilib-bootstrap.git/commit/?id=22181da2
Update README
Signed-off-by: Mike Gilbert <floppym <AT> gentoo.org>
README | 7 ++-----
1 file changed, 2 insertions(+), 5 deletions(-)
diff --git a/README b/README
index 83ffebc..d945570 100644
--- a/README
+++ b/README
@@ -13,16 +13,13 @@ How was this tarball generated?
/usr/lib64/gcc/x86_64-pc-linux-gnu/6.4.0/
to amd64
- The full list of directory names is:
- amd64 ilp32 ilp32d lp64 lp64d n32 n64 o32 ppc ppc64 s390 s390x x32 x86
-
* At the end run ./Cleanup to remove everything that is not needed
Current status:
-* lp64d, lp64, ilp32d, ilp32: Files from gcc-10.2
+* riscv/{lp64d,lp64,ilp32d,ilp32}: Files from gcc-10.2
* amd64, x86, ppc, ppc64: Files from gcc-9.3
* x32: Files from gcc-6.4
* s390, s390x: Files from gcc-5.4 (does this work?)
-* n32, n64, o32: last mips stages are years old, not useful
+* mips/{n32,n64,o32}: Files from gcc-11.2.1
next reply other threads:[~2022-04-17 17:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-17 17:48 Mike Gilbert [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-12-10 21:44 [gentoo-commits] proj/gcc-multilib-bootstrap:master commit in: / Andreas K. Hüttel
2020-12-10 19:38 Andreas K. Hüttel
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=1650215503.22181da2a393a2e3d47da511a49e958e649c15c0.floppym@gentoo \
--to=floppym@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