public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Maciej W. Rozycki <macro@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r11-9569] RISC-V: Add target machine headers as a dependency for riscv-sr.o Date: Mon, 14 Feb 2022 17:24:16 +0000 (GMT) [thread overview] Message-ID: <20220214172416.396DF3858C27@sourceware.org> (raw) https://gcc.gnu.org/g:d5781e740f9168754b659c013d5df63e30917f2f commit r11-9569-gd5781e740f9168754b659c013d5df63e30917f2f Author: Maciej W. Rozycki <macro@embecosm.com> Date: Mon Feb 14 17:23:11 2022 +0000 RISC-V: Add target machine headers as a dependency for riscv-sr.o Make riscv-sr.o depend on target machine headers, removing spurious test failures: FAIL: gcc.target/riscv/save-restore-3.c scan-assembler-not call[ \t]*t0,__riscv_save_0 FAIL: gcc.target/riscv/save-restore-3.c scan-assembler-not tail[ \t]*__riscv_restore_0 FAIL: gcc.target/riscv/save-restore-3.c scan-assembler tail[ \t]*foo FAIL: gcc.target/riscv/save-restore-6.c scan-assembler-not call[ \t]*t0,__riscv_save_0 FAIL: gcc.target/riscv/save-restore-6.c scan-assembler-not tail[ \t]*__riscv_restore_0 FAIL: gcc.target/riscv/save-restore-6.c scan-assembler tail[ \t]*other_func if the definitions of UNSPECs are locally changed and GCC rebuilt from a dirty tree. gcc/ * config/riscv/t-riscv (riscv-sr.o): Add $(TM_H) dependency. (cherry picked from commit 3faeba72cf93bdbf0b42d6b1b65fd4f0794f9d2a) Diff: --- gcc/config/riscv/t-riscv | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gcc/config/riscv/t-riscv b/gcc/config/riscv/t-riscv index 1215ea8b734..63b155ef154 100644 --- a/gcc/config/riscv/t-riscv +++ b/gcc/config/riscv/t-riscv @@ -6,7 +6,7 @@ riscv-builtins.o: $(srcdir)/config/riscv/riscv-builtins.c $(CONFIG_H) \ $(srcdir)/config/riscv/riscv-builtins.c riscv-sr.o: $(srcdir)/config/riscv/riscv-sr.c $(CONFIG_H) \ - $(SYSTEM_H) + $(SYSTEM_H) $(TM_H) $(COMPILER) -c $(ALL_COMPILERFLAGS) $(ALL_CPPFLAGS) $(INCLUDES) \ $(srcdir)/config/riscv/riscv-sr.c
reply other threads:[~2022-02-14 17:24 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=20220214172416.396DF3858C27@sourceware.org \ --to=macro@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: 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).