From: Cary Coutant <ccoutant@gmail.com>
To: Sriraman Tallam <tmsriram@google.com>
Cc: Xinliang David Li <davidxl@google.com>,
Richard Biener <richard.guenther@gmail.com>,
"H.J. Lu" <hjl.tools@gmail.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
binutils <binutils@sourceware.org>,
Yury Gribov <y.gribov@samsung.com>
Subject: Re: [RFC] COMDAT Safe Module Level Multi versioning
Date: Wed, 19 Aug 2015 04:53:00 -0000 [thread overview]
Message-ID: <CAJimCsF0uaxVKGTiHxTAW0yZgp57eCPj96-iFDACJ64_-CF_kg@mail.gmail.com> (raw)
In-Reply-To: <CAAs8HmwE5hBCv2H6g-o0QyBNSqS6c3Mhr=JCS+iNFMV=Q7=8bA@mail.gmail.com>
> Thanks, will make those changes. Do you recommend a different name
> for this flag like -fmake-comdat-functions-static?
Well, the C++ ABI refers to this as "vague linkage." It may be a bit
too long or too ABI-specific, but maybe something like
-f[no-]use-vague-linkage-for-functions or
-f[no-]functions-vague-linkage?
And perhaps note in the doc that using this option may technically
break the C++ ODR, so it should be used only when you know what you're
doing.
-cary
next prev parent reply other threads:[~2015-08-19 4:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-19 6:30 Sriraman Tallam
2015-05-19 9:39 ` Richard Biener
2015-05-19 16:12 ` Xinliang David Li
2015-06-17 2:18 ` Sriraman Tallam
2015-08-04 18:43 ` Sriraman Tallam
2015-08-13 6:17 ` Sriraman Tallam
2015-08-18 18:46 ` Sriraman Tallam
2015-08-18 21:19 ` Cary Coutant
2015-08-18 21:25 ` Cary Coutant
2015-08-18 21:44 ` Sriraman Tallam
2015-08-19 4:53 ` Cary Coutant [this message]
2015-09-03 0:51 ` Sriraman Tallam
2015-09-09 23:27 ` Sriraman Tallam
2015-10-05 21:58 ` Sriraman Tallam
2016-09-12 19:30 ` Sriraman Tallam
2015-05-19 17:22 ` Sriraman Tallam
2015-05-19 17:28 ` Yury Gribov
2015-05-19 18:18 ` Sriraman Tallam
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=CAJimCsF0uaxVKGTiHxTAW0yZgp57eCPj96-iFDACJ64_-CF_kg@mail.gmail.com \
--to=ccoutant@gmail.com \
--cc=binutils@sourceware.org \
--cc=davidxl@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hjl.tools@gmail.com \
--cc=richard.guenther@gmail.com \
--cc=tmsriram@google.com \
--cc=y.gribov@samsung.com \
/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).