public inbox for libc-testresults@sourceware.org help / color / mirror / Atom feed
From: Joseph Myers <joseph@codesourcery.com> To: <libc-testresults@sourceware.org> Subject: GCC mainline compilers 2023-05-02 09:14:47 build results Date: Tue, 2 May 2023 11:21:03 +0000 [thread overview] Message-ID: <168302646392.731025.5540672395220494792@build4-jammy-cs.sje.mentorg.com> (raw) Clean build with unchanged results. Component versions for this build: binutils: vcs-mainline (b2499d8a40a6de13e9bc88b973a730bdf8b9b032) gcc: vcs-mainline (87de39e4c3686535728f3a347f772e73af4cf262) glibc: vcs-mainline (e6a252758cbadb13654e66e1f2445ef6f8a4dea0) gmp: 6.2.1 (6.2.1) gnumach: vcs-mainline (61dfca567e982f2d6a0a25b04e9eb78adcaac370) hurd: vcs-mainline (0be50de40ee012223eba38e76f19ed08f5429f51) linux: 6.2 (6.2) mig: vcs-mainline (4c0f2ff0a1432f7e1794cf29b1a4667e3a0f8f89) mpc: 1.3.1 (1.3.1) mpfr: 4.2.0 (4.2.0)
reply other threads:[~2023-05-02 11:21 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=168302646392.731025.5540672395220494792@build4-jammy-cs.sje.mentorg.com \ --to=joseph@codesourcery.com \ --cc=libc-testresults@sourceware.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: linkBe 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 read-only IMAP folder(s) and NNTP newsgroup(s).