Adding gcc@gcc.gnu.org
On Wed, Jun 29, 2011 at 6:08 PM, Gabriel Charette <gch...@google.com> wrote: > > What's the purpose of weak_global_object_name? Defined in gcc/varasm.c > grepping from the base of the source recursively I only find this: > ./gcc/ChangeLog-1998: * varasm.c (assemble_start_function): Add > weak_global_object_name. > ./gcc/output.h:extern const char *weak_global_object_name; > ./gcc/ChangeLog-2000: weak_global_object_name here, as const char *. > ./gcc/ChangeLog-2000: first_global_object_name or weak_global_object_name. > Clean up string > ./gcc/ChangeLog-2000: * varasm.c (first_global_object_name, > weak_global_object_name): > ./gcc/tree.c: const char *name = weak_global_object_name; > ./gcc/ChangeLog-2005: (weak_global_object_name): Likewise. > ./gcc/varasm.c:extern GTY(()) const char *weak_global_object_name; > ./gcc/varasm.c:const char *weak_global_object_name; > ./gcc/varasm.c: Set first_global_object_name and weak_global_object_name as > appropriate. */ > ./gcc/varasm.c: type = &weak_global_object_name; > It seems like it's never actually set... some references to it are set... but > that seems like a very weird usage? And there is never any code that checks > whether `something == weak_global_object_name`... > I'm tempted to try to remove it... shall we ask Jason? > Gab
