From: "ben.boeckel" <ben.boeckel@kitware.com>
To: Iain Sandoe <iain@sandoe.co.uk>
Cc: GCC Development <gcc@gcc.gnu.org>,
Jonathan Wakely <jwakely.gcc@gmail.com>,
"chuanqi.xcq" <yedeng.yd@linux.alibaba.com>,
David Blaikie <dblaikie@gmail.com>,
Nathan Sidwell <nathanmsidwell@gmail.com>
Subject: Re: Naming flag for specifying the output file name for Binary Module Interface files
Date: Wed, 7 Dec 2022 11:29:16 -0500 [thread overview]
Message-ID: <Y5C/XDxbfXm6+12x@megas.dev.benboeckel.internal> (raw)
In-Reply-To: <6CFAC937-F5FD-49B3-A5E3-4ED83B270DCC@sandoe.co.uk>
On Wed, Dec 07, 2022 at 16:18:00 +0000, 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 contain many such modules (though they tend
to be looked up via include paths, so they are actually implicit builds
today; that may change if/when Fortran adopts P1689 as well).
--Ben
next prev parent reply other threads:[~2022-12-07 16: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 [this message]
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
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=Y5C/XDxbfXm6+12x@megas.dev.benboeckel.internal \
--to=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).