From: Ben Boeckel <ben.boeckel@kitware.com>
To: Boris Kolpackov <boris@codesynthesis.com>
Cc: gcc@gcc.gnu.org
Subject: Re: [modules] Preprocessing requires compiled header unit modules
Date: Thu, 21 Apr 2022 08:05:33 -0400 [thread overview]
Message-ID: <YmFIjb/GwaEX9GVQ@farprobe> (raw)
In-Reply-To: <boris.20220421055949@codesynthesis.com>
On Thu, Apr 21, 2022 at 06:05:52 +0200, Boris Kolpackov wrote:
> I don't think it is. A header unit (unlike a named module) may export
> macros which could affect further dependencies. Consider:
>
> import "header-unit.hpp"; // May or may not export macro FOO.
>
> #ifdef FOO
> import "header-unit2.hpp"
> #endif
I agree that the header needs to be *found*, but scanning cannot require
a pre-existing BMI for that header. A new mode likely needs to be laid
down to get the information necessary (instead of just piggy-backing on
`-E` behavior to get what I want).
--Ben
next prev parent reply other threads:[~2022-04-21 12:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-24 23:46 Ben Boeckel
2022-04-21 4:05 ` Boris Kolpackov
2022-04-21 12:05 ` Ben Boeckel [this message]
2022-04-21 17:59 ` Iain Sandoe
2022-04-21 18:08 ` Ben Boeckel
2022-04-21 18:18 ` Iain Sandoe
2022-04-22 14:08 ` Boris Kolpackov
2022-04-22 15:06 ` Iain Sandoe
2022-04-25 9:20 ` Boris Kolpackov
2022-04-22 16:05 ` Ben Boeckel
2022-04-25 9:42 ` Boris Kolpackov
2022-04-25 11:34 ` 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=YmFIjb/GwaEX9GVQ@farprobe \
--to=ben.boeckel@kitware.com \
--cc=boris@codesynthesis.com \
--cc=gcc@gcc.gnu.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).