public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jeff Law <law@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc(refs/vendors/riscv/heads/gcc-13-with-riscv-opts)] RISC-V: Add builtin .def file dependencies
Date: Tue, 26 Sep 2023 15:09:26 +0000 (GMT)	[thread overview]
Message-ID: <20230926150926.D247E3857BB3@sourceware.org> (raw)

https://gcc.gnu.org/g:948c265b1f35af8155fb32307925585edd6c8c83

commit 948c265b1f35af8155fb32307925585edd6c8c83
Author: Tsukasa OI <research_trasio@irq.a4lg.com>
Date:   Mon Sep 18 09:23:41 2023 +0000

    RISC-V: Add builtin .def file dependencies
    
    riscv-builtins.cc includes riscv-cmo.def and riscv-scalar-crypto.def
    (making dependencies) but their dependencies must be explicitly defined at
    the configuration file, t-riscv.
    
    They were the last two .def files without correct dependency information.
    
    gcc/ChangeLog:
    
            * config/riscv/t-riscv: Add dependencies for riscv-builtins.cc,
            riscv-cmo.def and riscv-scalar-crypto.def.
    
    (cherry picked from commit f45cca26263c3563e9db15e0ba64d4a114316808)

Diff:
---
 gcc/config/riscv/t-riscv | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/gcc/config/riscv/t-riscv b/gcc/config/riscv/t-riscv
index 104f85c6c8b..f137e1f17ef 100644
--- a/gcc/config/riscv/t-riscv
+++ b/gcc/config/riscv/t-riscv
@@ -8,7 +8,9 @@ riscv-builtins.o: $(srcdir)/config/riscv/riscv-builtins.cc $(CONFIG_H) \
   $(DIAGNOSTIC_CORE_H) $(OPTABS_H) $(RISCV_BUILTINS_H) \
   $(srcdir)/config/riscv/riscv-ftypes.def \
   $(srcdir)/config/riscv/riscv-vector-builtins-types.def \
-  $(srcdir)/config/riscv/riscv-modes.def
+  $(srcdir)/config/riscv/riscv-modes.def \
+  $(srcdir)/config/riscv/riscv-cmo.def \
+  $(srcdir)/config/riscv/riscv-scalar-crypto.def
 	$(COMPILER) -c $(ALL_COMPILERFLAGS) $(ALL_CPPFLAGS) $(INCLUDES) \
 		$(srcdir)/config/riscv/riscv-builtins.cc

                 reply	other threads:[~2023-09-26 15:09 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=20230926150926.D247E3857BB3@sourceware.org \
    --to=law@gcc.gnu.org \
    --cc=gcc-cvs@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).