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: stabilize .gcc_except_table with or without -g


> 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.


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