From: Gabriel Charette <gchare@google.com>
To: Diego Novillo <dnovillo@google.com>
Cc: reply@codereview.appspotmail.com, crowl@google.com,
gcc-patches@gcc.gnu.org
Subject: Re: [pph] Add header files to pph.map (issue4639073)
Date: Mon, 27 Jun 2011 17:53:00 -0000 [thread overview]
Message-ID: <BANLkTi=yxBWT1WE9-4Czew=cXQWCCg9Z4nNDAgWDm4t2p8_tRQ@mail.gmail.com> (raw)
In-Reply-To: <BANLkTinruTXXATrVdSxxaP9grw8bdnsqNQ@mail.gmail.com>
On Mon, Jun 27, 2011 at 10:18 AM, Diego Novillo <dnovillo@google.com> wrote:
> On Mon, Jun 27, 2011 at 13:13, Gabriel Charette <gchare@google.com> wrote:
>> On Mon, Jun 27, 2011 at 10:06 AM, Diego Novillo <dnovillo@google.com> wrote:
>>> On Mon, Jun 27, 2011 at 13:01, Gabriel Charette <gchare@google.com> wrote:
>>>> Couldn't we have headers look for their corresponding .pph file by
>>>> default when -fpph-map is on? (especially since pph.map is only
>>>> temporary for the implementation phase)
>>>
>>> The problem is with headers that include other headers. We want to
>>> limit the generation of images to specific headers. Given that we are
>>> in this initial implementation phase, the simplest approach is to
>>> remember to update pph.map.
>>
>> Well in what I'm proposing we only use the pph file if it was actually
>> generated before (we don't generate it if it's not there). Are there
>> any situations where we have a corresponding pph file, but don't
>> actually want to use it when the fpph-map flag is on? Seems unlikely
>> as we put all the pph files in the pph map for now anyways...
>
> Headers include other headers. We are not generating PPH for all headers.
>
> The mapping file also allows us to control what happens when
> generating a PPH file that emits #include directives itself. Some of
> those we want to have referenced as PPH, but not all.
>
> It's really easier for us to remember to update the mapping file
> rather than adding some automatic detection that would have to be
> removed later.
Ok I agree, temporary flags and map files are better then temporary
code for the implementation phase.
LGTM,
Gab
>
> Diego.
>
next prev parent reply other threads:[~2011-06-27 17:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-27 16:48 Diego Novillo
2011-06-27 17:06 ` Gabriel Charette
2011-06-27 17:10 ` Diego Novillo
2011-06-27 17:30 ` Gabriel Charette
2011-06-27 17:34 ` Diego Novillo
2011-06-27 17:53 ` Gabriel Charette [this message]
2011-06-27 19:24 ` Lawrence Crowl
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='BANLkTi=yxBWT1WE9-4Czew=cXQWCCg9Z4nNDAgWDm4t2p8_tRQ@mail.gmail.com' \
--to=gchare@google.com \
--cc=crowl@google.com \
--cc=dnovillo@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=reply@codereview.appspotmail.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).