From: "Marc Poulhiès" <dkm@kataplop.net>
To: gcc-patches@gcc.gnu.org
Cc: "Marc Poulhiès" <dkm@kataplop.net>
Subject: [COMMITTED] rust: fix link serialization [PR108113]
Date: Tue, 20 Dec 2022 09:15:49 +0100 [thread overview]
Message-ID: <20221220081549.339006-1-dkm@kataplop.net> (raw)
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>
---
Already reviewed and ACKed by Jakub: https://github.com/Rust-GCC/gccrs/pull/1704
bootstrapped on x86_64-linux with --enable-link-serialization=1 --enable-languages=c,c++,rust,lto.
Committed on master.
gcc/rust/Make-lang.in | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/gcc/rust/Make-lang.in b/gcc/rust/Make-lang.in
index 681ac7b3fee..713582cfe0c 100644
--- a/gcc/rust/Make-lang.in
+++ b/gcc/rust/Make-lang.in
@@ -35,6 +35,8 @@ GCCRS_TARGET_INSTALL_NAME := $(target_noncanonical)-$(shell echo gccrs|sed '$(pr
# Define the names for selecting rust in LANGUAGES.
rust: rust1$(exeext)
+rust.serial = rust1$(exeext)
+
# Tell GNU make to ignore files by these names if they exist.
.PHONY: rust
@@ -163,9 +165,11 @@ RUST_ALL_OBJS = $(GRS_OBJS) $(RUST_TARGET_OBJS)
rust_OBJS = $(RUST_ALL_OBJS) rust/rustspec.o
# The compiler itself is called rust1 (formerly grs1)
-rust1$(exeext): $(RUST_ALL_OBJS) attribs.o $(BACKEND) $(LIBDEPS)
+rust1$(exeext): $(RUST_ALL_OBJS) attribs.o $(BACKEND) $(LIBDEPS) $(rust.prev)
+ @$(call LINK_PROGRESS,$(INDEX.rust),start)
+$(LLINKER) $(ALL_LINKERFLAGS) $(LDFLAGS) -o $@ \
$(RUST_ALL_OBJS) attribs.o $(BACKEND) $(LIBS) $(BACKENDLIBS)
+ @$(call LINK_PROGRESS,$(INDEX.rust),end)
# Build hooks.
--
2.39.0
reply other threads:[~2022-12-20 8:16 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=20221220081549.339006-1-dkm@kataplop.net \
--to=dkm@kataplop.net \
--cc=gcc-patches@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).