This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH]: random global function name

From: Alexandre Oliva <aoliva at redhat dot com>
To: kaih at khms dot westfalen dot de (Kai Henningsen)
Cc: gcc-patches at gcc dot gnu dot org
Date: 11 Jul 2003 13:42:41 -0300
Subject: Re: [PATCH]: random global function name
Organization: GCC Team, Red Hat
References: <3F06F3F4.3020600@codesourcery.com><20030708225503.GB481@redhat.com> <878yr8haau.fsf@codesourcery.com><878yr8haau.fsf@codesourcery.com> <20030709000930.GI481@redhat.com><8pcGAsvmw-B@khms.westfalen.de>

On Jul 10, 2003, kaih@khms.westfalen.de (Kai Henningsen) wrote:

> I'm pretty certain a md5 collision is far less likely than just about  
> every reasonable expectation you can come up with. This fear is entirely  
> spurious.

> It's also what rsync relies on.

So does ccache.  I've never had a collision, and I'm pretty sure the
linker would notice if I did.

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                 aoliva@{redhat.com, gcc.gnu.org}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist                Professional serial bug killer

Follow-Ups:
- Re: [PATCH]: random global function name
  - From: Eric Christopher

References:
- [PATCH]: random global function name
  - From: Nathan Sidwell
- Re: [PATCH]: random global function name
  - From: Richard Henderson
- Re: [PATCH]: random global function name
  - From: Zack Weinberg
- Re: [PATCH]: random global function name
  - From: Richard Henderson
- Re: [PATCH]: random global function name
  - From: Kai Henningsen

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]