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 #1201
Date: Wed,  8 Jun 2022 12:42:06 +0000 (GMT)	[thread overview]
Message-ID: <20220608124206.E740C386CE67@sourceware.org> (raw)

https://gcc.gnu.org/g:694114ea9567d1d7bc96b3d5ce287daede11b941

commit 694114ea9567d1d7bc96b3d5ce287daede11b941
Merge: fb136314f95 cf9d65a9136
Author: bors[bot] <26634292+bors[bot]@users.noreply.github.com>
Date:   Mon May 2 19:38:51 2022 +0000

    Merge #1201
    
    1201: Generic functions should not be TREE_PUBLIC r=philberty a=philberty
    
    Generic functions cannot be public since the symbols could overlap in
    linking other crates reusing the same generic. The other benefit here is
    that when optimizations are turned on we can eliminate more code since the
    symbol does not _need_ to be public.
    
    
    Co-authored-by: Philip Herron <philip.herron@embecosm.com>

Diff:

 gcc/rust/backend/rust-compile-base.cc | 8 +++++---
 gcc/rust/backend/rust-compile-base.h  | 2 +-
 2 files changed, 6 insertions(+), 4 deletions(-)


                 reply	other threads:[~2022-06-08 12:42 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=20220608124206.E740C386CE67@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: 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).