top | item 29780686

(no title)

egberts | 4 years ago

I’ve embarked down this same path with GCC 2.7.4 from a … while … back.

Ingo is on the right track.

I’ve always thought that this stuff should have been dealt with by the GCC (in form of pre-cached header files).

So sad that it is a thorny issue to this day (for large scale projects); so glad that this issue is now alive so it can be dealt with once and for all.

I envision some type of *.ho filetype to hold these quasi-compiled headers for the next build iteration.

discuss

order

pas|4 years ago

"... dealt with once and for all."

Is at least one GCC maintainer looking at this? Otherwise it'll likely not be dealt with "for all", right?

On the kernel side every new dependency has to be added with keeping in mind this problem as long as there's no automation to help with this it'll be a problem.

folmar|4 years ago

Do you mean .pch? I think it works quite well generally, but for the kernel it might be too fragile as it is not so widely used.