Diego Novillo <dnovi...@google.com> a écrit:
> On Thu, Apr 26, 2012 at 06:43, Dodji Seketeli <do...@seketeli.org> wrote:
>
>> I guess it's also worth noting one limitation of PPHs that is, if I
>> believe the wiki:
>>
>> In essence, the only headers that can be pre-parsed are those that
>> produce the same result when they are compiled in isolation or as
>> part of another translation unit. So, header files that are affected
>> by pre-processor symbols defined before inclusion are not going to
>> be considered (e.g., stddef.h).
>>
>> [1]: http://gcc.gnu.org/wiki/pph#Scope_and_limitations
>>
>> How hard would it be to drop that limitation?
>
> It's an explicit non-goal, actually. If you relax this requirements,
> you might as well re-parse the header file. The work needed to make
> flexible PPH images will rob you of most/all the performance you were
> looking for.
I see. Thank you for the clarification.
One more question, for my education. Does the PPH machinery detect that
a given header doesn't respect that requirement and thus refuses to
serialize it?
--
Dodji
