Re: Naming flag for specifying the output file name for Binary Module Interface files

On Thu, Dec 15, 2022 at 07:37:35 +, Iain Sandoe wrote: > * 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

Re: Naming flag for specifying the output file name for Binary Module Interface files

- > From:Nathan Sidwell > Send Time:2022年12月15日(星期四) 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 Mod

Re: Naming flag for specifying the output file name for Binary Module Interface files

ect: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 th

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 c

Re: Naming flag for specifying the output file name for Binary Module Interface files

t; indicated (potentially leaving an older version there), or does the > > equivalent > > of 'rm -f $MODULE.pcm' happen? > > > > The module file will be deleted. The behavior is the same with `-o`. > > > > Thanks, > > Chuanqi > > > &

Re: Naming flag for specifying the output file name for Binary Module Interface files

rom:Nathan Sidwell > Send Time:2022年12月12日(星期一) 22:30 > To:Iain Sandoe ; GCC Development > Cc:Nathan Sidwell ; Jonathan Wakely > ; David Blaikie ; ben.boeckel > ; chuanqi.xcq > Subject:Re: Naming flag for specifying the output file name for Binary Module > Interface files >

Re: Naming flag for specifying the output file name for Binary Module Interface files

f 'rm -f $MODULE.pcm' happen? > > The module file will be deleted. The behavior is the same with `-o`. > > Thanks, > Chuanqi > > > -- > From:Nathan Sidwell > Send Time:2022年12月12日(星期一) 22:30 > To:Iain Sandoe ; GCC Develop

Re: Naming flag for specifying the output file name for Binary Module Interface files

ben.boeckel ; chuanqi.xcq Subject:Re: Naming flag for specifying the output file name for Binary Module Interface files On 12/9/22 12:33, Iain Sandoe wrote: > Hello all. > >> On 9 Dec 2022, at 01:58, chuanqi.xcq wrote: >> >> It looks like `-fmodule-file` is better from

Re: Naming flag for specifying the output file name for Binary Module Interface files

On 12/9/22 12:33, Iain Sandoe wrote: Hello all. On 9 Dec 2022, at 01:58, chuanqi.xcq wrote: It looks like `-fmodule-file` is better from the discussion. So let's take it. Thanks for everyone here So FAOD (after this discussion) Chuanqi's current patchset implements the following in clang:

Re: Naming flag for specifying the output file name for Binary Module Interface files

, > > Chuanqi > > -- > > From:Nathan Sidwell > > Send Time:2022年12月8日(星期四) 01:00 > > To:Iain Sandoe ; GCC Development > > Cc:Jonathan Wakely ; chuanqi.xcq > > ; David Blaikie ; >

Re: Naming flag for specifying the output file name for Binary Module Interface files

e ; > ben.boeckel > Subject:Re: Naming flag for specifying the output file name for Binary Module > Interface files > > On 12/7/22 11:58, Iain Sandoe wrote: > > > > > >> On 7 Dec 2022, at 16:52, Nathan Sidwell via Gcc wrote: > >> > >> On 12/7

Re: Naming flag for specifying the output file name for Binary Module Interface files

akely ; chuanqi.xcq ; David Blaikie ; ben.boeckel Subject:Re: Naming flag for specifying the output file name for Binary Module Interface files On 12/7/22 11:58, Iain Sandoe wrote: > > >> On 7 Dec 2022, at 16:52, Nathan Sidwell via Gcc wrote: >> >> On 12/7/22 11:18, Iain

Re: Naming flag for specifying the output file name for Binary Module Interface files

On 12/7/22 11:58, Iain Sandoe wrote: On 7 Dec 2022, at 16:52, Nathan Sidwell via Gcc wrote: On 12/7/22 11:18, Iain Sandoe wrote: I think it is reasonable to include c++ in the spelling, since other languages supported by GCC (and clang in due course) have modules. I disagree (about the

Re: Naming flag for specifying the output file name for Binary Module Interface files

> On 7 Dec 2022, at 16:52, Nathan Sidwell via Gcc wrote: > > On 12/7/22 11:18, Iain Sandoe wrote: > >> I think it is reasonable to include c++ in the spelling, since other >> languages supported by >> GCC (and clang in due course) have modules. > > I disagree (about the reasonableness part)

Re: Naming flag for specifying the output file name for Binary Module Interface files

On 12/7/22 11:18, Iain Sandoe wrote: I think it is reasonable to include c++ in the spelling, since other languages supported by GCC (and clang in due course) have modules. I disagree (about the reasonableness part). Other languages have modules, true, but if they want to name the output fi

Re: Naming flag for specifying the output file name for Binary Module Interface files

On 12/7/22 10:23, Jonathan Wakely wrote: On Wed, 7 Dec 2022, 02:30 chuanqi.xcq via Gcc, > wrote: \ (2) If (1) is not acceptable and we love to keep the command line consistency, I think clang can use '-fmodule-output=' as long as we make it clear in the do

Re: Naming flag for specifying the output file name for Binary Module Interface files

On Wed, Dec 07, 2022 at 16:18:00 +, Iain Sandoe wrote: > I think it is reasonable to include c++ in the spelling, since other > languages supported by > GCC (and clang in due course) have modules. Especially given that Fortran doesn't necessarily have one module to output; Fortran sources can

Re: Naming flag for specifying the output file name for Binary Module Interface files

Hi Folks, > On 7 Dec 2022, at 15:45, ben.boeckel via Gcc wrote: > > On Wed, Dec 07, 2022 at 15:23:09 +, Jonathan Wakely wrote: >> I disagree. I can easily remember "module output" but I would have to check >> the manual every time to see if it's "std c++ module save file" or some >> other pe

Re: Naming flag for specifying the output file name for Binary Module Interface files

On Wed, Dec 07, 2022 at 15:23:09 +, Jonathan Wakely wrote: > I disagree. I can easily remember "module output" but I would have to check > the manual every time to see if it's "std c++ module save file" or some > other permutation of those words I can say that in developing the CMake side of t

Re: Naming flag for specifying the output file name for Binary Module Interface files

On Wed, 7 Dec 2022, 02:30 chuanqi.xcq via Gcc, wrote: > Hi Nathan, > > 1) 'save' -- does it *cause* the bmi to be saved, or is that actually > controlled > by other options? (I suspect the latter) > Yes, it causes the bmi to be saved. In fact, when we add `-save-temps` > option in clang and we co

Re: Naming flag for specifying the output file name for Binary Module Interface files

llo.pcm -c -o Hello.o ``` If you are interested, you can take a look at: https://clang.llvm.org/docs/StandardCPlusPlusModules.html#quick-start Thanks, Chuanqi -------------- From:Nathan Sidwell Send Time:2022年12月7日(星期三) 08:35 To:David Blaikie ; gcc Mailing List ; Iain San

Re: Naming flag for specifying the output file name for Binary Module Interface files

On Wed, 7 Dec 2022, 00:36 Nathan Sidwell via Gcc, wrote: > On 12/6/22 16:03, David Blaikie wrote: > > Over in https://reviews.llvm.org/D137059 we're discussing the naming > > of a clang flag - would be good to have it be consistent with GCC. > > > > The functionality is to name the BMI (.pcm in C

Re: Naming flag for specifying the output file name for Binary Module Interface files

On 12/6/22 16:03, David Blaikie wrote: Over in https://reviews.llvm.org/D137059 we're discussing the naming of a clang flag - would be good to have it be consistent with GCC. The functionality is to name the BMI (.pcm in Clang's parlance) output file when compiling a C++20 module. Current propo

Naming flag for specifying the output file name for Binary Module Interface files

Over in https://reviews.llvm.org/D137059 we're discussing the naming of a clang flag - would be good to have it be consistent with GCC. The functionality is to name the BMI (.pcm in Clang's parlance) output file when compiling a C++20 module. Current proposal is to use `-fsave-std-cxx-module-file