public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Rainer Orth <ro@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r13-6139] rust: Fix rust-tree.cc compilation on SPARC Date: Mon, 20 Feb 2023 10:41:02 +0000 (GMT) [thread overview] Message-ID: <20230220104102.1B589382CD4D@sourceware.org> (raw) https://gcc.gnu.org/g:7b8916a6fd098546e4e53e53b37a5153664ba17f commit r13-6139-g7b8916a6fd098546e4e53e53b37a5153664ba17f Author: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE> Date: Mon Feb 20 11:40:24 2023 +0100 rust: Fix rust-tree.cc compilation on SPARC This patch commit 27a89f84c458ae938bc3eb92ad0d594c06fc3b42 Author: Thomas Schwinge <thomas@codesourcery.com> Date: Fri Feb 17 23:36:20 2023 +0100 '#include "tm_p.h"' in 'gcc/rust/backend/rust-tree.cc' broke rust bootstrap on SPARC: In file included from ./tm_p.h:4, from /vol/gcc/src/hg/master/local/gcc/rust/backend/rust-tree.cc:38: /vol/gcc/src/hg/master/local/gcc/config/sparc/sparc-protos.h:46:47: error: use of enum 'memmodel' without previous declaration 46 | extern void sparc_emit_membar_for_model (enum memmodel, int, int); | ^~~~~~~~ Fixed by including memmodel.h. Tested on sparc-sun-solaris2.11 and i386-pc-solaris2.11. 2023-02-20 Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE> gcc/rust: * backend/rust-tree.cc: Include memmodel.h. Diff: --- gcc/rust/backend/rust-tree.cc | 1 + 1 file changed, 1 insertion(+) diff --git a/gcc/rust/backend/rust-tree.cc b/gcc/rust/backend/rust-tree.cc index e2595b59aa8..d2d170c23f1 100644 --- a/gcc/rust/backend/rust-tree.cc +++ b/gcc/rust/backend/rust-tree.cc @@ -35,6 +35,7 @@ #include "file-prefix-map.h" #include "cgraph.h" #include "output.h" +#include "memmodel.h" #include "tm_p.h" // forked from gcc/c-family/c-common.cc c_global_trees
reply other threads:[~2023-02-20 10:41 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=20230220104102.1B589382CD4D@sourceware.org \ --to=ro@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).