public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Iain Sandoe <iain@sandoe.co.uk>
To: GCC Development <gcc@gcc.gnu.org>
Cc: David Blaikie <dblaikie@gmail.com>,
	Nathan Sidwell <nathanmsidwell@gmail.com>,
	Jonathan Wakely <jwakely.gcc@gmail.com>,
	"chuanqi.xcq" <yedeng.yd@linux.alibaba.com>,
	"ben.boeckel" <ben.boeckel@kitware.com>
Subject: Re: Naming flag for specifying the output file name for Binary Module Interface files
Date: Thu, 15 Dec 2022 07:37:35 +0000	[thread overview]
Message-ID: <5C1A2971-2E02-400D-A2F1-3AD96E4038CC@sandoe.co.uk> (raw)
In-Reply-To: <4a2c3667-ae49-4a04-bb41-b20cee9ddb3e.yedeng.yd@linux.alibaba.com>



> On 15 Dec 2022, at 05:58, chuanqi.xcq <yedeng.yd@linux.alibaba.com> wrote:
> 
> Hi Nathan,
> 
> > 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)?
> 
> 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 ‘module mapper’ 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


> 
> Thanks,
> 
> Chuanqi
> 
> ------------------------------------------------------------------
> From:Nathan Sidwell <nathan@acm.org>
> Send Time:2022年12月15日(星期四) 06:29
> 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
> 
> 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
> 


  reply	other threads:[~2022-12-15  7:37 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
2022-12-15  5:58                                 ` chuanqi.xcq
2022-12-15  7:37                                   ` Iain Sandoe [this message]
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=5C1A2971-2E02-400D-A2F1-3AD96E4038CC@sandoe.co.uk \
    --to=iain@sandoe.co.uk \
    --cc=ben.boeckel@kitware.com \
    --cc=dblaikie@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --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).