This is the mail archive of the
mailing list for the GDB project.
Re: (toplevel) Fix dramatic breakage for ordinary crosses (related to program_transform_name)
- From: Ben Elliston <bje at redhat dot com>
- To: gdb-patches at sources dot redhat dot com
- Cc: binutils at sources dot redhat dot com,gcc-patches at gcc dot gnu dot org
- Date: 06 Jan 2003 11:04:25 +1100
- Subject: Re: (toplevel) Fix dramatic breakage for ordinary crosses (related to program_transform_name)
- Organization: Red Hat Asia-Pacific Pty Ltd
- References: <200212282057.gBSKva103446@duracef.shout.net>
>>>>> "Michael" == Michael Elizabeth Chastain <firstname.lastname@example.org> writes:
Michael> I would also prefer no locks, because I don't want to deal
Michael> with locking mechanism headaches when a user with, say, an
Michael> SMP Irix NFS client and an HP/UX NFS server has funny build
I have been pondering this problem. It's a shame Autoconf just can't
be fixed (and patches even backported to 2.13, if necessary) to change
the structure of the cache. These locking problems exist because the
cache values are kept in a single file and to control access via a
single lock would be too coarse grained.
If, instead, the cache were a "dot" directory that contained files
whose filenames had the form "key=value", then test results could be
examined or updated using atomic file system operations and there
should be no races.
Michael> So I'm in favor of a dumb, simple, and reliable mechanism
Michael> to serialize the configures.
I think the performance of large configure runs is becoming too poor
to take this line for much longer.