This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: multiple definitions of 'xxx keyed to...' in egcs-1.1.1
- To: hjl at lucon dot org
- Subject: Re: multiple definitions of 'xxx keyed to...' in egcs-1.1.1
- From: Mark Mitchell <mark at markmitchell dot com>
- Date: Mon, 15 Feb 1999 17:49:02 -0800
- CC: law at cygnus dot com, martin at mira dot isdn dot cs dot tu-berlin dot de, egcs at egcs dot cygnus dot com
- References: <m10CYsJ-00038sC@ocean.lucon.org>
- Reply-to: mark at markmitchell dot com
>>>>> "H" == H J Lu <hjl@lucon.org> writes:
H> Here is my proposal. main () in toplev.c calls unique_string ()
H> to initialize a static variable in tree.c:
In my opinion, this is not a good proposal. In another life, I work
on issues of computer security, and silently putting things that might
reveal the hostname where the program is compiled in .o files is not
at all a good thing.
If we can make the functions static, the problem goes away, right? If
not, then sufficiently many random bits is just fine. I would guess
that 2048 would be more than enough for quite some time to come.
--
Mark Mitchell mark@markmitchell.com
Mark Mitchell Consulting http://www.markmitchell.com