From: Nathan Sidwell <nathan@acm.org>
To: David Blaikie <dblaikie@gmail.com>,
"chuanqi.xcq" <yedeng.yd@linux.alibaba.com>
Cc: Iain Sandoe <iain@sandoe.co.uk>,
GCC Development <gcc@gcc.gnu.org>,
Nathan Sidwell <nathanmsidwell@gmail.com>,
Jonathan Wakely <jwakely.gcc@gmail.com>,
"ben.boeckel" <ben.boeckel@kitware.com>
Subject: Re: Naming flag for specifying the output file name for Binary Module Interface files
Date: Wed, 14 Dec 2022 17:29:41 -0500 [thread overview]
Message-ID: <af2b5b48-2e2d-a9d8-ca39-d16c509e2248@acm.org> (raw)
In-Reply-To: <CAENS6Es=5t24iPa2U02toi=fgwaL6miX7ybF9Ht3E3fq6Mdhjg@mail.gmail.com>
I'm missing something from this discussion. IIUC the claim is that these 2 new
options -fmodule-output{,=NAME} are for build systems that want to specify the
module output file.
But how do they specify the mapping from module/header-unit name to CMI, so that
imports work?
Is this really a clang-specific mechanism, as it has no module mapper ATM (IIUC)?
nathan
--
Nathan Sidwell
next prev parent reply other threads:[~2022-12-14 22:29 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-06 21:03 David Blaikie
2022-12-07 0:35 ` Nathan Sidwell
2022-12-07 1:45 ` Jonathan Wakely
2022-12-07 2:30 ` chuanqi.xcq
2022-12-07 15:23 ` Jonathan Wakely
2022-12-07 15:45 ` ben.boeckel
2022-12-07 16:18 ` Iain Sandoe
2022-12-07 16:29 ` ben.boeckel
2022-12-07 16:52 ` Nathan Sidwell
2022-12-07 16:58 ` Iain Sandoe
2022-12-07 17:00 ` Nathan Sidwell
2022-12-09 1:58 ` chuanqi.xcq
2022-12-09 17:33 ` Iain Sandoe
2022-12-09 17:43 ` David Blaikie
2022-12-12 14:30 ` Nathan Sidwell
2022-12-13 3:10 ` chuanqi.xcq
2022-12-13 15:56 ` David Blaikie
2022-12-14 9:56 ` chuanqi.xcq
2022-12-14 18:39 ` David Blaikie
2022-12-14 22:29 ` Nathan Sidwell [this message]
2022-12-15 5:58 ` chuanqi.xcq
2022-12-15 7:37 ` Iain Sandoe
2022-12-15 13:21 ` ben.boeckel
2022-12-07 16:43 ` Nathan Sidwell
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=af2b5b48-2e2d-a9d8-ca39-d16c509e2248@acm.org \
--to=nathan@acm.org \
--cc=ben.boeckel@kitware.com \
--cc=dblaikie@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=iain@sandoe.co.uk \
--cc=jwakely.gcc@gmail.com \
--cc=nathanmsidwell@gmail.com \
--cc=yedeng.yd@linux.alibaba.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).