https://gcc.gnu.org/bugzilla/show_bug.cgi?id=15351

pskocik at gmail dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |pskocik at gmail dot com

--- Comment #3 from pskocik at gmail dot com ---
>From my reading of the manual, which talks about a *.gch precompiled-header
directory, it seems to me like gcc would be in the perfect position to manage
that directory itself. If the directory has a header matching the current
compiler config, it should use it, otherwise, it should create a new entry and
use that.

The user could simply tell gcc which header it wants precompiled and gcc could
take care of creating the precompiled versions in the appropriate gch directory
as needed.

(If gcc were to manage the *.gch directory itself, it wouldn't also need to try
all directory entries until a match is found -- it could aim directly, based
its established naming system for the entries. The naming system could be such
so that entries from uninstalled compiler versions could be automatically or
manually deleted.)

The cache directories could be in the same directory as the found header, or in
a per-user system-directory that pararellizes the path of the found header in
case the directory of the found header isn't writable by the current user.

Reply via email to