From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-rust@gcc.gnu.org
Subject: [Bug rust/108113] Rust and --enable-link-serialization=1
Date: Tue, 20 Dec 2022 08:12:09 +0000 [thread overview]
Message-ID: <bug-108113-35322-FKHmE7MAZw@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108113-35322@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108113
--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Marc Poulhi?s <dkm@gcc.gnu.org>:
https://gcc.gnu.org/g:02c031088ac0bbf716aec52e027d615b7a5a572b
commit r13-4804-g02c031088ac0bbf716aec52e027d615b7a5a572b
Author: Marc Poulhiès <dkm@kataplop.net>
Date: Wed Dec 14 21:29:13 2022 +0100
rust: fix link serialization [PR108113]
The Make-lang.in was missing the link serialization support.
PR rust/108113
gcc/rust
* Make-lang.in (rust.serial): New variable.
(rust1$(exeext)): Depend on $(rust.prev). Call LINK_PROGRESS.
Signed-off-by: Marc Poulhiès <dkm@kataplop.net>
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-12-20 8:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-14 19:49 [Bug rust/108113] New: " jakub at gcc dot gnu.org
2022-12-14 19:59 ` [Bug rust/108113] " dkm at gcc dot gnu.org
2022-12-14 21:01 ` dkm at gcc dot gnu.org
2022-12-16 18:35 ` tschwinge at gcc dot gnu.org
2022-12-19 8:54 ` dkm at gcc dot gnu.org
2022-12-19 11:42 ` tschwinge at gcc dot gnu.org
2022-12-19 11:49 ` jakub at gcc dot gnu.org
2022-12-20 8:12 ` cvs-commit at gcc dot gnu.org [this message]
2022-12-20 8:32 ` dkm at gcc dot gnu.org
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=bug-108113-35322-FKHmE7MAZw@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-rust@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).