public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jason Merrill <jason@redhat.com>
To: Ben Boeckel <ben.boeckel@kitware.com>, gcc-patches@gcc.gnu.org
Cc: nathan@acm.org, fortran@gcc.gnu.org, gcc@gcc.gnu.org,
	brad.king@kitware.com
Subject: Re: [PATCH v8 0/4] P1689R5 support
Date: Tue, 19 Sep 2023 17:33:34 -0400	[thread overview]
Message-ID: <99ce75f4-a654-581c-30f7-7fce16b8106e@redhat.com> (raw)
In-Reply-To: <20230901130407.259768-1-ben.boeckel@kitware.com>

On 9/1/23 09:04, Ben Boeckel wrote:
> Hi,
> 
> This patch series adds initial support for ISO C++'s [P1689R5][], a
> format for describing C++ module requirements and provisions based on
> the source code. This is required because compiling C++ with modules is
> not embarrassingly parallel and need to be ordered to ensure that
> `import some_module;` can be satisfied in time by making sure that any
> TU with `export import some_module;` is compiled first.
> 
> [P1689R5]: https://isocpp.org/files/papers/P1689R5.html
> 
> I've also added patches to include imported module CMI files and the
> module mapper file as dependencies of the compilation. I briefly looked
> into adding dependencies on response files as well, but that appeared to
> need some code contortions to have a `class mkdeps` available before
> parsing the command line or to keep the information around until one was
> made.
> 
> I'd like feedback on the approach taken here with respect to the
> user-visible flags. I'll also note that header units are not supported
> at this time because the current `-E` behavior with respect to `import
> <some_header>;` is to search for an appropriate `.gcm` file which is not
> something such a "scan" can support. A new mode will likely need to be
> created (e.g., replacing `-E` with `-fc++-module-scanning` or something)
> where headers are looked up "normally" and processed only as much as
> scanning requires.
> 
> FWIW, Clang as taken an alternate approach with its `clang-scan-deps`
> tool rather than using the compiler directly.
> 
> Thanks,
> 
> --Ben
> 
> ---
> v7 -> v8:
> 
> - rename `DEPS_FMT_` enum variants to `FDEPS_FMT_` to match the
>    associated flag
> - memory leak fix in the `join` specfunc implementation (also better
>    comments), both from Jason
> - formatting fix in `mkdeps.cc` for `write_make_modules_deps` assignment
> - comments on new functions for P1689R5 implementation

Pushed, thanks!

Jason


  parent reply	other threads:[~2023-09-19 21:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-01 13:04 Ben Boeckel
2023-09-01 13:04 ` [PATCH v8 1/4] spec: add a spec function to join arguments Ben Boeckel
2023-09-01 13:04 ` [PATCH v8 2/4] p1689r5: initial support Ben Boeckel
2023-09-01 13:04 ` [PATCH v8 3/4] c++modules: report imported CMI files as dependencies Ben Boeckel
2023-09-01 13:04 ` [PATCH v8 4/4] c++modules: report module mapper files as a dependency Ben Boeckel
2023-09-19 21:33 ` Jason Merrill [this message]
2023-09-20 14:44   ` [PATCH v8 0/4] P1689R5 support Ben Boeckel

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=99ce75f4-a654-581c-30f7-7fce16b8106e@redhat.com \
    --to=jason@redhat.com \
    --cc=ben.boeckel@kitware.com \
    --cc=brad.king@kitware.com \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=nathan@acm.org \
    /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).