From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp002.apm-internet.net (smtp002.apm-internet.net [85.119.248.221]) by sourceware.org (Postfix) with ESMTPS id D85793856B65 for ; Thu, 15 Dec 2022 07:37:41 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org D85793856B65 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=sandoe.co.uk Authentication-Results: sourceware.org; spf=none smtp.mailfrom=sandoe.co.uk Received: (qmail 97396 invoked from network); 15 Dec 2022 07:37:36 -0000 X-APM-Out-ID: 16710898569739 X-APM-Authkey: 257869/1(257869/1) 6 Received: from unknown (HELO smtpclient.apple) (81.138.1.83) by smtp002.apm-internet.net with SMTP; 15 Dec 2022 07:37:36 -0000 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.1\)) Subject: Re: Naming flag for specifying the output file name for Binary Module Interface files From: Iain Sandoe In-Reply-To: <4a2c3667-ae49-4a04-bb41-b20cee9ddb3e.yedeng.yd@linux.alibaba.com> Date: Thu, 15 Dec 2022 07:37:35 +0000 Cc: David Blaikie , Nathan Sidwell , Jonathan Wakely , "chuanqi.xcq" , "ben.boeckel" Content-Transfer-Encoding: quoted-printable Message-Id: <5C1A2971-2E02-400D-A2F1-3AD96E4038CC@sandoe.co.uk> References: <96699ff0-f4d7-4276-8af7-5a4ce9735174@acm.org> <6CFAC937-F5FD-49B3-A5E3-4ED83B270DCC@sandoe.co.uk> <2f005f8a-5e96-aece-c654-ab4b090da409@acm.org> <29c9ff1a-2c88-4e02-81e0-9780020b8e77.yedeng.yd@linux.alibaba.com> <3c9bfafd-9898-ca67-b629-5a23fec58792@acm.org> <41caec52-1372-4441-b62d-6ce33f3534c6.yedeng.yd@linux.alibaba.com> <4a2c3667-ae49-4a04-bb41-b20cee9ddb3e.yedeng.yd@linux.alibaba.com> To: GCC Development X-Mailer: Apple Mail (2.3696.120.41.1.1) X-Spam-Status: No, score=-6.7 required=5.0 tests=BAYES_00,BODY_8BITS,KAM_COUK,KAM_DMARC_STATUS,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW,SPF_HELO_NONE,SPF_NONE,TXREP autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: > On 15 Dec 2022, at 05:58, chuanqi.xcq = wrote: >=20 > Hi Nathan, >=20 > > But how do they specify the mapping from module/header-unit name to = CMI, so that=20 > > imports work? > > > > Is this really a clang-specific mechanism, as it has no module = mapper ATM (IIUC)? >=20 > Yes, clang doesn't have a module mapper. And I remember Iain said he = want to introduce these options in GCC. To clarify: * I have patches for clang that implements the P1184 interface which = would allow a =E2=80=98module mapper=E2=80=99 to be used to discover = module name <-> pathname pairings. * The demand for the command line options we are discussing here is = coming from build systems folks who want to be able to specify = everything on the command line (i.e. from my understanding they do not = want to use a module mapper, but prefer dependency scanning). So I think the two aspects are somewhat independent, I would expect the = same build systems folks to want to be able to specify everything on the = GCC command line too. thanks, Iain >=20 > Thanks, >=20 > Chuanqi >=20 > ------------------------------------------------------------------ > From:Nathan Sidwell > Send Time:2022=E5=B9=B412=E6=9C=8815=E6=97=A5(=E6=98=9F=E6=9C=9F=E5=9B=9B= ) 06:29 > To:David Blaikie ; chuanqi.xcq = > Cc:Iain Sandoe ; GCC Development ; = Nathan Sidwell ; Jonathan Wakely = ; ben.boeckel > Subject:Re: Naming flag for specifying the output file name for Binary = Module Interface files >=20 > I'm missing something from this discussion. IIUC the claim is that = these 2 new=20 > options -fmodule-output{,=3DNAME} are for build systems that want to = specify the=20 > module output file. >=20 > But how do they specify the mapping from module/header-unit name to = CMI, so that=20 > imports work? >=20 > Is this really a clang-specific mechanism, as it has no module mapper = ATM (IIUC)? >=20 > nathan > --=20 > Nathan Sidwell >=20