This is the mail archive of the
mailing list for the GCC project.
Re: stabilize .gcc_except_table with or without -g
- From: DJ Delorie <dj at redhat dot com>
- To: aoliva at redhat dot com
- Cc: gcc-patches at gcc dot gnu dot org
- Date: Mon, 5 Nov 2007 15:41:08 -0500
- Subject: Re: stabilize .gcc_except_table with or without -g
- References: <firstname.lastname@example.org>
> Should new the compare function be moved into libiberty proper?
If it were to be moved into libiberty, I think (1) it would need to
guard against NULL arguments, and (2) it must assume that two strings
may compare equal. Libiberty functions shouldn't abort if they can
return a meaningful error value.
As for should it be in libiberty... I think it would be reasonable for
each hash type to have a "stock" implementation of hashing a simple
string. Sometimes it would be useful, but at least it would serve as
an example upon which to build application-specific hashes.