public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Thomas Schwinge <tschwinge@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc/devel/rust/master] Merge #916 Date: Wed, 8 Jun 2022 12:05:02 +0000 (GMT) [thread overview] Message-ID: <20220608120502.4309A3AA901B@sourceware.org> (raw) https://gcc.gnu.org/g:f6ba472caf42db1f5f2f98b73afccf448b36c322 commit f6ba472caf42db1f5f2f98b73afccf448b36c322 Merge: 6d1ff568084 c598bbbcc1e Author: bors[bot] <26634292+bors[bot]@users.noreply.github.com> Date: Thu Feb 10 12:50:30 2022 +0000 Merge #916 916: Support inline attribute by marking as DECL_DECLARED_INLINE_P r=philberty a=philberty This does a refactor by removing more flags for the fndecl construction from the rust-gcc wrapper code in favour of using the tree api directly. The ABI option attributes have also been refactored from the backend interface in favour of their own package. The gccgo wrapper tried to mark inline fns as extern inline but this refactor allows us to control the inline options specificly for the rust semantics. Fixes #857 Co-authored-by: Philip Herron <philip.herron@embecosm.com> Diff: gcc/rust/Make-lang.in | 2 + gcc/rust/backend/rust-compile-base.cc | 92 +++++++++++++++++++++++ gcc/rust/backend/rust-compile-base.h | 6 ++ gcc/rust/backend/rust-compile-extern.h | 11 +-- gcc/rust/backend/rust-compile-implitem.h | 17 ++--- gcc/rust/backend/rust-compile-item.h | 24 +++--- gcc/rust/hir/tree/rust-hir-item.h | 4 + gcc/rust/rust-backend.h | 69 +---------------- gcc/rust/rust-gcc.cc | 61 +-------------- gcc/rust/typecheck/rust-hir-type-check-implitem.h | 20 +++-- gcc/rust/util/rust-abi.cc | 64 ++++++++++++++++ gcc/rust/{ => util}/rust-abi.h | 8 ++ 12 files changed, 214 insertions(+), 164 deletions(-)
reply other threads:[~2022-06-08 12:05 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=20220608120502.4309A3AA901B@sourceware.org \ --to=tschwinge@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).