This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Database for GCC
- From: "J.C. Pizarro" <jcpiza at gmail dot com>
- To: "Tom Browder" <tom dot browder at gmail dot com>, "GCC Development" <gcc at gcc dot gnu dot org>
- Date: Tue, 29 Apr 2008 16:27:23 +0200
- Subject: Re: Database for GCC
On Tue, 29 Apr 2008 08:16:14 -0500, "Tom Browder" <tom.browder@gmail.com> wrote:
> A naive thought, perhaps:
>
> Would there be any advantage to using a key-value embedded database
> program for the voluminous maps needed for gcc optimization, etc.?
>
> If so, consider <http://tokyocabinet.sourceforge.net>.
>
> I have used its predecessor, qdbm, for years and it was very fast. TC
> is faster still.
>
> I notice many threads here about memory requirements and speed
> reductions--perhaps there is some way TC could help with those
> problems.
>
> -Tom
It's interesting but this database manager TC as the SQLite are
non-concurrent or non-parallel libraries versus their perspective
another libraries DB4 and MySQL that can be concurrent or
parallel.
But it's not a general problem. You can use them using filelocks
but the access to this database manager is non-concurrent.
The applicability of TC for GCC can be enormeus:
* for storing compiled objects with many attributes of information.
* for storing profiles of the runs.
* for storing logs of the compilations of experimental GCC.
* for browsing this locked database for track the internal details of GCC.
* etc.
J.C.Pizarro